Consider the following script:
vim -u NONE -N /proc/meminfo /proc/cpuinfo -c next -c $ARG
where $ARG is one of
Next 1 ++enc=ucs4
Next 1 +echomsg1
Next /proc/cpuinfo
. In the first case it is expected to open /proc/meminfo in UCS4 encoding, but
it does not. It will if you remove 1.
In the second case it is expected to echo 1, but it does not. It will if you
remove 1.
In the third case it is expected to complain about invalid argument (Next does
not accept file names). Instead it silently switches to /proc/meminfo like if
this argument was not supplied. (Failing may mitigate the first two issues.)
Note about first two commands: according to the documentation [count] should be
placed *before* ++opt and +cmd, not after. Actually you cannot place them
there. It is not only :Next that is subject to this problem: I have not
actually tested, but all of :previous, :sNext, :sarguments and :sprevious must
be subject to these issues (documentation is correct for :sarguments and
:sprevious: [N] is placed at the end).
(Replace /proc/cpuinfo and /proc/meminfo with some readable non-empty files if
you do not have them in the system.)
--
--
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.
