> This problem occurs in vim with +multi_byte.
> :edit ++encoding=xyz always causes error E474, while ++enc=xyz succeeds.
>
> "encoding" is the only ++option where the short form of the option is a
> substring of the long form. The check for these options does not account
> for this.
>
> Here is one way to fix this (same as attached patch).
Thanks for the patch, I'll look into it soon.
--
ARTHUR: This new learning amazes me, Sir Bedevere. Explain again how sheep's
bladders may be employed to prevent earthquakes.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- Br...@Moolenaar.net -- 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 ///
On Dec 9, 7:24 pm, Charles Cooper <sabl...@gmail.com> wrote:
> This problem occurs in vim with +multi_byte.
> :edit ++encoding=xyz always causes error E474, while ++enc=xyz succeeds.
>
> "encoding" is the only ++option where the short form of the option is a
> substring of the long form. The check for these options does not account
> for this.
>
This is confusing, because ++enc actually modifies 'fileencoding', not
'encoding'. I think this potentially makes it even more confusing.
++enc and ++encoding are already both foreseen, but the current code
tests for ++enc first, and for ++encoding only if ++enc was not found,
which is wrong. The patch just reverses the order of the already
existing tests.
The case of ++bin / ++binary / ++nobin / ++nobinary is already handled
by the existing code.
Best regards,
Tony.
--
Ten years of rejection slips is nature's way of telling you to stop
writing.
-- R. Geis