Thank you very much Ben for your great explication.
Not easy to understand.
I still don't understand why my vimrc and menu.vim, containing both french
characters as œu, could be read in latin1 in the past, without any problem or
error.
(The only encoding line I had in my vimrc file at that
Den 6 jul 2014 01:03 skrev Ben Fritz fritzophre...@gmail.com:
On Saturday, July 5, 2014 5:26:15 PM UTC-5, Mark Volkmann wrote:
I'm trying to use syntax region with start=regex and end=regex, but
having difficulty.
I want the region to match what follows the start regex and precedes
the end
See also http://vim.wikia.com/wiki/Working_with_Unicode
You seem to have read that article, which I wrote myself, so I'll try to
explain in more detail (I hope not in boring detail) the logic behind
it. Be sure to check the Vim help for anything which would still be unclear.
'encoding' is a
Tim Chase wrote:
Can anyone reproduce the following, and if so, is this a bug?
vim -u NONE -N
(start vim with no .vimrc in 'nocompatible' mode)
ihelloesc
(insert some text on the first line)
Y
(yank the line)
:reg
(correctly shows that and 0 contain the yanked
On Sunday, July 6, 2014 5:32:32 AM UTC-5, rameo wrote:
Thank you very much Ben for your great explication.
Not easy to understand.
Agreed, encoding stuff is hard to understand in the best of cases. I think
Vim's mix of 4 options (enc, fenc, fencs, tenc), one of which (fenc) is
On Saturday, July 5, 2014 4:01:51 PM UTC-7, Ben Fritz wrote:
That would be because your :map! command applies also to command-line mode,
because you did not specify a specific mode for it to apply in (for example,
:imap or :inoremap). This causes a problem because your first mapping, for
Let's set up a 2-line file:
hello
world
and have fun with the q command. You need to restart Vim before every example.
q~q
:di reveals ~ has been written to and 0, which isn't that unusual.
ddq~q
still matches 1, and q only wrote to 0. That's odd.
ddq1~q
This wrote to and 1, but 0 is
