Say I'm editing my _vimrc
file and I've just added a couple of lines, for instance a new key mapping. I don't want to reload the whole file (:so %
) since that will reset a lot of temporary stuff I'm experimenting with. I just want to run the two lines that I'm currently working on.
I'm having no luck trying to copy/paste the lines into the command buffer, since I can't use the put command in there. Is there any way I could run the current line (or current selection) as EX commands?
Summary:
After Anton Kovalenko's answer and Peter Rincker's comment I ended up with these key maps, which either executes the current line, or the current selected lines if in visual mode:
" Execute current line or current selection as Vim EX commands.
nnoremap <F2> :exe getline(".")<CR>
vnoremap <F2> :<C-w>exe join(getline("'<","'>"),'<Bar>')<CR>
To execute the current line as an ex command, you may also use:
This will yank the current line to the "-register and execute it. I don't think it is too much typing.
The accepted answer doesn't handle continuation sections. Also, surprisingly, the bar isn't needed, newlines are fine. This will work, first yanking the text into register x:
As someone has already mentioned, the only exception are commands that "eat up" newlines. Eg, executing the above mapping on:
will cause vim to to think that the user is trying to define textl as "Search\n:exe ":sign place... etc.
If you want to execute a command because you want to refine it before committing it to _.vimrc, then you should launch a Command Line Window for Ex-mode commands with q:.
At launch the Command Line Window is buffered with the contents of the command line history. It is a normal Vim window the contents of which can be edited as any text buffer with the exception of pressing on any line which executes the command on that line. It is very useful when you want to slightly change a long, complex command you wrote earlier and re-run it.
To launch a 'Command Line Window' for search strings press q/.
For that purpose, I have defined the following commands and mappings:
If you're doing a lot of experimenting (trying things out that you might want to add to your vimrc, I assume?) it might help to do so in a scratch file like experimental.vim so you aren't just relying on your history to know what you're trying out. Now that you have these great mappings, it will be easy to rerun things from experimental or vimrc without sourcing the whole file.
Also (sorry, I can't comment on answers yet, it seems), I tried this mapping of Peter's:
This works in most cases, but it fails specifically on function definitions.
This mapping joins the lines into a single string, separated by
<BAR>
and then execs them.I'm not entirely sure why, but if I try to do that with a function definition in normal mode:
After some testing, I've found that it will work with newline separators instead:
So, I've changed my mapping to this:
I suppose there is a vim or ex reason why the
<BAR>
method doesn't work on functions (maybe even some setting I have on?), and I'm curious to hear what it is if someone knows.Executing the line under cursor as an Ex command:
Convenient enough for 2 lines.
(I'd figure out something for doing it with regions, but I'm not a vim user). And for currently selected region, the following seems to do the job:As commented by Peter Rincker, this mapping can be used for executing the currently selected lines: