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.
OK. But why do you not tell me how you use. The only way I know of is with something like cat. First I type 'cat foo.txt' <Enter>. I now select, paste and ctrl-D. If instead I select, and run vim, when I paste vim simply puts me in Insert mode.
You need to be in insert mode to paste text into vi, since it otherwise interprets the text as commands. Also, why Ctrl+D?
Coders frequently turn their nose up at a mouse, as if it were some smelly newbie tool, and as if they could do the same tasks faster without the mouse...
So how, in console, would they move blocks of text within the same file, or between separate files, more quickly than if they were using a mouse: with the "kill" and "yank" features of emacs, or course! It turns out, that if you can teach your fingers to memorize zillions of emacs keybard shortcuts, then you won't want a mouse.
It really depends on the environment along with the task at hand. Not all coders look at the mouse in the since you are speaking. But enhance their operation by integrating work with the mouse with keys or options. Really depends on personal taste and tasks at hand.
Some use emacs' while others still slumber along with 'vi/vim'. You move marked text to the the buffer/file then insert where you wish. Or just insert a file at a specific point within the body. Just learn the commands of the editor of choice. 'emacs' is extensible thus allowing a versatile editor.
I use 'vi/vim' more now since it will be available on most Gnu/Linux. Be sure to look at the initial screen for vim for useful information. While in 'vim' try command mode(esc) & type ':help' (without tics) to get started. Or type ':help subject' (to get help on a specific subject). Neat when you are in a split window to get the options/strokes you do not use all the time.
If you happen to need a IDE then a mouse is doable and sometimes easier in combination with option(s) command keys while in the editor. So it means you can really move around freely within but at the restriction(s) of the IDE. If you use KDE on your Slack machine you have KDevelop else;
Actually testing now I see that it does work for me between virtual consoles. For some reason I thought it didn't. Ah well I'd still prefer use screen or better yet tmux. It is handy to split the viewable area into parts that you can view at the same time, without having to constantly switch between virtual consoles.
Last edited by ruario; 09-20-2011 at 01:49 AM.
Reason: spelling
When pasting in vim you have to press the 'Shift' key as well. Just tried this with two konsoles and it worked, but when I tried in in an actual console mode it didn't. Worked okay with elvis. Maybe an issue with vim. I'm sure it worked before.
With the addition of the Shift key trick it works. But same as you: only with vi and with two VTs.
In fact, my primary motivation is the famous quotations making there entrance once one has logged in. Some of them are worth saving. But this thing usefulness is ample.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.