Vi and Vim Stack Exchange is a question and answer site for people using the vi and Vim families of text editors. It only takes a minute to sign up.
Sign up to join this community
I have
which means
My meanings for these keys clashes with vim's idea that stdin needs to be saved, e.g.
$ git log | vim -No write since last change ...And I can then quit.
How can I tell vim to ignore file saving when using "-" to read for input from stdin?
I would start vim with a command that tells it the current file is a scratch buffer (which vim will not prompt you to save):
git log | vim -c "setlocal buftype=nofile bufhidden=hide noswapfile" -
Because I do this a lot, I save the scratch buffer settings to a command in my .vimrc
":ScratchBuffer makes current buffer disposable
command! ScratchBuffer setlocal buftype=nofile bufhidden=hide noswapfile
I also add a bash function in my .bashrc
v() {
vim -c ScratchBuffer -
}
This means I can type git log | v to achieve the desired effect
StdinReadPre and StdinReadPost autocmds, which could be used to do this for you automatically. You could also use the VimEnter autocmd, but then you can't distinguish between reading from stdin and just typing vim with no arguments (my answer here actually does something very similar).
– Martin Tournoij
Mar 25 '15 at 19:27
You can run vim in read-only mode (as you're not opening a proper file):
git log | vim -R -
Then standard q should work, without asking you to save your changes.
vim -: anything sent to stderr is interpreted by vim as a command. To avoid this, you'd want to redirect stderr to stdout:git log 2>&1 | vim -– Matt Boehm Mar 25 '15 at 14:46qis very handy and used to record macros (see:h q). You may want to think about a different set of keys for you mapping. Maybe use a<leader>. See:h mapleader. – Peter Rincker Mar 25 '15 at 16:53qmapped toexitin bash,sys.exit()in python, and so weiter. – jalanb Mar 25 '15 at 23:21