ZyX wrote:
> If you type `:bufdo $append<CR>` vim will start iterating over
> buffers. Each time buffer is entered $append asks for input. But
>
> 1. Buffer is not shown in the window, neither there are any messages
> about which buffer is being processed.
> 2. It is hard to understand that cursor in the command-line without
> :bufdo… command-line shown has something to do with append.
> 3. There is no visual indication of append finishing receiving input.
>
> To check:
>
> vim -u NONE xxx-unexistent-file-{1,2,3} -c 'set hidden' -s <(echo ':windo
> $append')
>
> (windo has the same problems, I can safely assume this is also the
> case for tabdo and argdo). Then type e.g.
> `abc<CR>.<CR>def<CR>.<CR>ghi<CR>.<CR>`. The point is not in typing,
> you should analyze the vim view during it: it is not possible to
> deduce what is going on until everything is over.
Can you use something else than ":append"? It's really a leftover from
old days.
--
SOLDIER: What? A swallow carrying a coconut?
ARTHUR: It could grip it by the husk ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
