On 21/03/14 07:34, ZyX wrote:
The following script will echo 1 three times without any errors in place of
complaining about missing endif:
vim -u NONE 1 2 3 -c 'bufdo while 1 | echo 1'
. The following script will ask user three times for endif:
vim -u NONE 1 2 3 -s<(echo ':bufdo if 1 | echo 1')
.
Isn't this to do with the fact that "<(...)" causes the shell to create
a temporary file
which is then sourced by ViM, and in ViM, all block constructs must be
terminated
by the end of the current file, therwise an error occurs.
"-c" on the other hand simply executes an Ex command as if it had been
entered
interactively by the user. There is no file scope therefore there is no
error output if
the end of the block is missing.
To me it looks like ViM is working normally here.
Cheers,
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.