Vim Tips Wiki
(→‎Comments: The original code wasn't owrking.)
Tags: Visual edit apiedit
(Added reference to Tim Pope's vim-unimpaired plugin.)
Tag: sourceedit
(One intermediate revision by one other user not shown)
Line 28: Line 28:
 
==Comments==
 
==Comments==
 
It's also a nice idea to map something like
 
It's also a nice idea to map something like
  +
<pre>
nnoremap <C-J> i<CR><Esc>
+
nnoremap <C-J> a<CR><Esc>k$
  +
</pre>
  +
 
because it's the opposite of Shift-J. A more sophisticated solution would be
 
because it's the opposite of Shift-J. A more sophisticated solution would be
 
<pre>
 
<pre>
Line 75: Line 78:
 
The command-line window can operate in normal or insert mode and in both <code><CR></code> executes the command from current line. Using <code>nmap</code> instead of <code>map</code> in the mapping declaration partially fixes the problem. Then, to execute the command, you must enter the insert mode and press <code><CR></code>. While this is a feasible workaround, I prefer to dispense with this mapping and type <code>oii</code> to insert a new line (<code>ii</code> being my map for <code><Esc></code>).
 
The command-line window can operate in normal or insert mode and in both <code><CR></code> executes the command from current line. Using <code>nmap</code> instead of <code>map</code> in the mapping declaration partially fixes the problem. Then, to execute the command, you must enter the insert mode and press <code><CR></code>. While this is a feasible workaround, I prefer to dispense with this mapping and type <code>oii</code> to insert a new line (<code>ii</code> being my map for <code><Esc></code>).
 
:Excellent point! <code>:map</code> applies to too many modes, I went ahead and made it <code>:nmap</code>. For the other problem, we should edit the mapping to detect the command-line window, like in [[Syntax folding of Vim scripts]]. Probably this will need an <code><expr></code> form of the mapping to do easily. --[[User:Fritzophrenic|Fritzophrenic]] ([[User talk:Fritzophrenic|talk]]) 15:01, June 27, 2013 (UTC)
 
:Excellent point! <code>:map</code> applies to too many modes, I went ahead and made it <code>:nmap</code>. For the other problem, we should edit the mapping to detect the command-line window, like in [[Syntax folding of Vim scripts]]. Probably this will need an <code><expr></code> form of the mapping to do easily. --[[User:Fritzophrenic|Fritzophrenic]] ([[User talk:Fritzophrenic|talk]]) 15:01, June 27, 2013 (UTC)
  +
  +
----
  +
'''Just use Tim Pope's excellent vim-unimpaired plugin'''
  +
The plugin provides the following two mappings:
  +
<code>[<Space></code> and <code>]<Space></code> add newlines before and after the cursor line.
  +
  +
https://github.com/tpope/vim-unimpaired

Revision as of 12:53, 10 August 2015

Tip 982 Printable Monobook Previous Next

created 2005 · complexity basic · author Christopher Auer · version 5.7


As you all may know with 'o' or 'O' you can insert a new line after/before the current line. But both commands enter the insert mode, which may sometimes not be what you want. I put this in my vimrc-file to insert a new-line after the current line by pressing Enter (Shift-Enter for inserting a line before the current line):

nmap <S-Enter> O<Esc>
nmap <CR> o<Esc>

If you want to stay in the line where you have been before use the following maps:

nmap <S-Enter> O<Esc>j
nmap <CR> o<Esc>k

See also

Comments

It's also a nice idea to map something like

nnoremap <C-J> a<CR><Esc>k$

because it's the opposite of Shift-J. A more sophisticated solution would be

nnoremap <C-J> ciW<CR><Esc>:if match( @", "^\\s*$") < 0<Bar>exec "norm P-$diw+"<Bar>endif<CR>

For whatever reason, I was unable to get the suggest mapping with <S-Enter> and <CR> to work properly (both ended up inserting below). So I did:

nmap <F8> o<Esc>
nmap <F9> O<Esc>

Which works fine for me.


<S-Enter> and <CR> will work separately in gvim but not in urxvt. See http://stackoverflow.com/questions/598113/can-terminals-detect-shift-enter-or-control-enter


Referencing the above, the default terminal on MacOS returns ^M with all modifier keys.

If you don't use return to navigate in normal mode, you can remap two returns to insert a new line:

:nmap <CR><CR> o<ESC>

Since I have inoremap jj <Esc> in my .vimrc, it take not too much to type ojj or Ojj.


To add a blank line below or above and keep the cursor in place, I think this is easiest:

nnoremap <C-J> m`o<Esc>``
nnoremap <C-K> m`O<Esc>``

It uses the jump list to remember the cursor position, so it does clutter up that list. But I don't mind. You could use any other mark, like so (uses mark a):

nnoremap <C-J> mao<Esc>`a
nnoremap <C-K> maO<Esc>`a


This mapping interferes with command execution in the command-line window. The command-line window can operate in normal or insert mode and in both <CR> executes the command from current line. Using nmap instead of map in the mapping declaration partially fixes the problem. Then, to execute the command, you must enter the insert mode and press <CR>. While this is a feasible workaround, I prefer to dispense with this mapping and type oii to insert a new line (ii being my map for <Esc>).

Excellent point! :map applies to too many modes, I went ahead and made it :nmap. For the other problem, we should edit the mapping to detect the command-line window, like in Syntax folding of Vim scripts. Probably this will need an <expr> form of the mapping to do easily. --Fritzophrenic (talk) 15:01, June 27, 2013 (UTC)

Just use Tim Pope's excellent vim-unimpaired plugin The plugin provides the following two mappings: [<Space> and ]<Space> add newlines before and after the cursor line.

https://github.com/tpope/vim-unimpaired