Vim Tips Wiki
Register
We recommend that you log in before editing. This will allow other users to leave you a message about your edit, and will let you track edits via your Watchlist. Creating an account is quick and free.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 22: Line 22:
   
 
set mouse=a
 
set mouse=a
set nu
+
se nu
   
 
:map <C-a> GVgg
 
:map <C-a> GVgg
Line 75: Line 75:
   
 
----
 
----
If You don't want to lose some of vim's powerfull commands its' WORTH TO READ BENEATH!
 
 
 
I don't think I'd ever recommend anything like this, without offering replacements for the lost functionality. Almost everything you use here overrides a very useful built-in command.
 
I don't think I'd ever recommend anything like this, without offering replacements for the lost functionality. Almost everything you use here overrides a very useful built-in command.
   
Line 107: Line 105:
 
::Thanks to Baliganikhil for the new tip, but Fritzophrenic is correct: Vim users should work how to use Vim ([[Tutorial]] is the start of an attempt to provide guidance), so these mappings are more of a current individual preference than general advice. Perhaps this should be moved to a user page?
 
::Thanks to Baliganikhil for the new tip, but Fritzophrenic is correct: Vim users should work how to use Vim ([[Tutorial]] is the start of an attempt to provide guidance), so these mappings are more of a current individual preference than general advice. Perhaps this should be moved to a user page?
 
::I do agree about Ctrl-A/C/V/X: when I used Konversation for the first time (the IRC client with KDE on Linux) I wondered how to copy some of the messages, and sure enough Ctrl-C worked. About that time I decided that Vim old timers had lost the battle over those keys, and I worked out how to properly map them (I intend fixing [[VimTip356|356 Quick yank and paste]] one day). However, mapping Ctrl-C to <code>y</code> is not helpful. I only use Ctrl-C/V for copy/paste with other applications: within Vim, it is essential to learn the basics like <code>y</code> and <code>p</code>. Also, it is never a good idea to map a key that is easy to press for <code>:q!</code> because sooner or later the key will be pressed accidentally and a lot of work will be lost. [[User:JohnBeckett|JohnBeckett]] 10:38, May 4, 2012 (UTC)
 
::I do agree about Ctrl-A/C/V/X: when I used Konversation for the first time (the IRC client with KDE on Linux) I wondered how to copy some of the messages, and sure enough Ctrl-C worked. About that time I decided that Vim old timers had lost the battle over those keys, and I worked out how to properly map them (I intend fixing [[VimTip356|356 Quick yank and paste]] one day). However, mapping Ctrl-C to <code>y</code> is not helpful. I only use Ctrl-C/V for copy/paste with other applications: within Vim, it is essential to learn the basics like <code>y</code> and <code>p</code>. Also, it is never a good idea to map a key that is easy to press for <code>:q!</code> because sooner or later the key will be pressed accidentally and a lot of work will be lost. [[User:JohnBeckett|JohnBeckett]] 10:38, May 4, 2012 (UTC)
 
----
 
I think that the above reply paired with the original tip is very useful. For example, I never use tags (maybe that's my fault?) but I find it very convenient to have a hotkey for opening a new tab, and vim doesn't provide this. I can rest assured that, at least for the time being, I haven't lost any functionality that I might care about, and now I've learned some new commands about tagging that might help me in the future.
 
 
This is a nice summary of what "normal hotkeys" do in vim. Very convenient as a reference.
 
 
18:08:2014 - a guest added the first line of comments - he could never know about that vim's native commands. Thanks to <small>[[User:Fritzophrenic|Fritzophrenic]], </small>he knows now.
 
Please note that all contributions to the Vim Tips Wiki are considered to be released under the CC-BY-SA
Cancel Editing help (opens in new window)

Template used on this page: