SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No doubt vim has a workaround for the case of this user and of mine. Or something went wrong in the installation. But the fact is I had no problem with vi.
You can see it at the cinematographic industry as well, and literature of course. If a movie has the number 2 in its title, you bet its a bad one. Of course there are exceptions.
I set mouse=r in my vimrc since I only ever use the mouse for copy/paste and have no problems whatsoever pasting.
But there is another alternative: did you know that vim keeps a buffer between sessions? - ie you can copy from a file open in vim using the usual vim visual mode, close that file, open second file and paste.
I did not think I had to be so explicit. First part= vi. Second part= vim. And you see a user and me are having problems pasting with vim. But no problem at all with vi. Second part, in the saying, means that that comes after, a sequel.
No doubt vim has a workaround for the case of this user and of mine. Or something went wrong in the installation. But the fact is I had no problem with vi.
You can see it at the cinematographic industry as well, and literature of course. If a movie has the number 2 in its title, you bet its a bad one. Of course there are exceptions.
'vim' is the improved 'vi'. Most Gnu/Linux ship with 'vim' or vi which is a link to 'elvis on my machine';
DESCRIPTION
Elvis is a text editor. It is intended to be a modern replacement for the classic
ex/vi editor of UNIX fame. Elvis supports many new features, including multiple
edit buffers, multiple windows, multiple user interfaces (including an X11 inter-
face), and a variety of display modes.
To exit Elvis, you can give the command ":q" in each of its windows. If you've
modified the buffer in a window, and you want to abandon those changes, then give
the command ":q!" instead.
Again, please check your system 'man' for explanation(s). Look through the install and find out what is linked to what;
It is about ten years now, that I run elvis. One day, I found vi is a link to elvis in slackware. Some years ago, I discovered vim. I have read the expression Vi IMproved many a time before your post.
What I see, is that using vim or emacs, takes reading a thousand helps to do the tiniest thing. Else you must have a vim curriculum. Is vi so awful? And what I was trying to mean with my saying, is that vim was, perhaps, an unnecessary addition. Another saying. Why to fix it if it's not broken?
And may be one day you slow down with your "read-the-man-pages-thing". I would appreciate it.
It is about ten years now, that I run elvis. One day, I found vi is a link to elvis in slackware. Some years ago, I discovered vim. I have read the expression Vi IMproved many a time before your post.
What I see, is that using vim or emacs, takes reading a thousand helps to do the tiniest thing. Else you must have a vim curriculum. Is vi so awful? And what I was trying to mean with my saying, is that vim was, perhaps, an unnecessary addition. Another saying. Why to fix it if it's not broken?
And may be one day you slow down with your "read-the-man-pages-thing". I would appreciate it.
It is obvious that you do not use available documentation with the continued type of queries that are made.
How else will you learn? Either by experimentation or utilize available information to help you perform or do operations without delay by using what is at hand.
What I see, is that using vim or emacs, takes reading a thousand helps to do the tiniest thing. Else you must have a vim curriculum. Is vi so awful? And what I was trying to mean with my saying, is that vim was, perhaps, an unnecessary addition. Another saying. Why to fix it if it's not broken?
If you don't care about making use of Vim-specific features that aren't in vi, you can learn using the same resources you use to learn vi.
Also, Vim isn't an unnecessary addition. It has many great features that I use all the time, mainly tabs and syntax highlighting.
What I see, is that using vim or emacs, takes reading a thousand helps to do the tiniest thing. Else you must have a vim curriculum. Is vi so awful? And what I was trying to mean with my saying, is that vim was, perhaps, an unnecessary addition. Another saying. Why to fix it if it's not broken?
While I can't help you with the issues you're having with copy and paste in virtual terminals (I very rarely use them, also don't have gpm installed to test it), I wanted to chime in and comment on your remark about Vim being an "unnecessary addition".
You're comparing vim with vi, but the fact is that vi you're using is another clone of it, elvis (at least it is in default Slackware installation). There's a reason why we have clones now and not the original vi: it wasn't free software back then (only recently it was released as BSD software). That is, there was a real need to create these "unnecessary additions". And it's only natural for software to evolve when people use it and see new ways to improve it, hence why both vim and elvis (yes, it has more features than original vi) have various enhancements like multiple buffers, windows, etc. Here's another example which I couldn't live without and which vim does have: multiple undo levels. Original vi lacks it. Elvis lacks it (unless there's an option for that which is turned off by default).
Is vim complex? Definitely. Do you have to use all its features? Not at all. Use what you really need. And you can still enjoy some very handy additions like the ones I already mentioned. If you find elvis a better choice, stick with it. I believe it's a fine alternative (though I've used it only a few times).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.