How to redirect ex command output into current buffer or file?

by 
:redir >name_of_registers_file
:registers
:redir END
:r name_of_registers_file
:help redir

The last command is very useful, since there are lots of options for redirection: to variables, to registers, how to append, further cornucopia.

I still find it weird and annoying that it uses END that way, but since everything else that can follow redir has to start with a non-word-character, at least it’s not ambiguous.

PS AFAIK (which is pretty far in this case) there’s no way to read it directly into the buffer: you have to store it in a register or a variable first. Check the help for the various options of how to do that.

PPS If you do want to do this using a variable —maybe to encapsulate it in a function and avoid clobbering registers or global variables— you’ll have to convert the multiline string that gets written to the variable into a list. EG

:call append( '.', split(variable_you_redirected_to, "\n") )

Otherwise (if you just do append('.',var)) you end up with ^@’s (nulls) instead of newlines, since that’s what vimscript uses to represent newlines in String variables.

edit: as @Bill Odom mentions, using :put =variable_you_redirected_to is a lot easier than the complicated append() expression. Thanks, Bill!

PPPS

I’ve written a snippet to make this stuff more convenient. It declares a function Redir(command, target) and a command R.

The command parses the last series of non-space characters as a redirection target and passes that to the function, which does the boilerplate to redirect the command output to the redirection target.

The command is everything after R and before the last space.

EG

" Store the vim buffer list in buffer_list.txt
:R ls >buffer_list.txt
" Store error messages emitted by a function being debugged
"   in the 'unnamed register'
:R call FunctionBeingDebugged() @">

There are a few limitations with this: for example you won’t be able to write to a filename that contains a space. The upside to this is that you don’t have to quote your command. I’ve got it posted on gist.github.com, and I’ll try to keep it updated if I end up improving it. Or you can fork it yourself</noeuphemism>!

Anyway the snippet is available here. It can be dropped into a .vimrc file or into a file in ~/.vim/plugins.

More Related Contents:

  1. What is the difference between the remap, noremap, nnoremap and vnoremap mapping commands in Vim?
  2. How to create an alias for a command in Vim?
  3. Multiple commands on same line
  4. How to make vim paste from (and copy to) system’s clipboard?
  5. vim change :x function to delete buffer instead of save & quit
  6. How does the vim “write with sudo” trick work?
  7. How to stop vim from adding a newline at end of file?
  8. How to convert the ^M linebreak to ‘normal’ linebreak in a file opened in vim?
  9. Why does Vim save files with a ~ extension?
  10. In Vim is there a way to delete without putting text in the register?
  11. How to get visually selected text in VimScript
  12. How to map Shift-Enter
  13. Saving vim macros
  14. Can vim monitor realtime changes to a file
  15. How do I make Vim do normal (Bash-like) tab completion for file names?
  16. What is the in a .vimrc file?
  17. How to prevent vim from creating (and leaving) temporary files?
  18. vim, switching between files rapidly using vanilla Vim (no plugins)
  19. Working with huge files in VIM
  20. Smart Wrap in Vim
  21. cscope or ctags why choose one over the other? [closed]
  22. Vim – how to run a command immediately when starting vim?
  23. How to map Ctrl+A and Ctrl+Shift+A differently?
  24. Get rid of Vim’s highlight after searching text
  25. Vim: Pipe selected text to shell cmd and receive output on vim info/command line
  26. Why would Vim add a new line at the end of a file?
  27. Pathogen does not load plugins
  28. How to open a file in a list of files in Vim?
  29. Does Vim load plugins after loading vimrc?
  30. Enabling markdown highlighting in Vim

Leave a Comment