Reply to message «Re: [BUG] Passing special characters to &listchars and &fillchars causes screen corruption», sent 18:57:07 06 August 2011, Saturday by Tony Mechelynck:
I don't use google groups and I received U+00B6, not U+015B. Anyway, I also really *like* google groups changing my « into << and doing other bad things when I type Russian text. Original message: > On 06/08/11 16:17, Tony Mechelynck wrote: > > On 06/08/11 15:31, ZyX wrote: > >> Consider the following code: > >> > >> vim -u NONE -c $'set list lcs=nbsp:\x0D' \ > >> -c $'normal! i\u00A0\u00A0\u00A0a\e' > >> > >> You will see cursor placed on the second virtual `M' (from `^M'), but > >> `ga' will > >> show that you are on the letter `a'. Passing special characters to `tab' > >> suboption causes more corruption, but is less reproducible. With > >> fillchars > >> results are better: highlighting partially disappears, but that's all > >> (tested > >> only with vert and stl). > > > > That code is invalid, see :help 'listchars' > > > > UTF-8 characters can be used when 'encoding' is "utf-8", > > otherwise only printable characters are allowed. All characters > > must be single width > > > > I suppose a more adequate formulation would be: > > > > Only single-width printable characters are allowed. > > Multibyte characters are allowed only if 'encoding' is "utf-8". > > > > The bug, if there is one, is that > > > > :set list lcs=nbsp:\x0D > > > > (with a non-printable character) does not generate an error (I get "E474 > > Invalid argument", which IMO is no bug.) > > > > I'm on gvim 7.3.269, Huge build with GTK2/Gnome GUI, under utf-8 > > 'encoding'. My "usual" 'list'/'listchars' setting is > > > > :set list lcs=eol:ś,tab:\|_,nbsp:~,conceal:* > > > > but even temporarily trying to set only > > > > :set list=\x0D > > > > gives me the above-mentioned error, and 'listchars' is not modified. > > > > > > Best regards, > > Tony. > > ...and for some reason that f???ing bl??dy st??id googlegroups interface > changed my Pilcrow mark to an s-acute. Well, the exact character used > there is irrelevant in this case but still, I don't like it. The copy in > my "Sent" folder is in 8bit ISO-8859-1 with the correct Pilcrow mark; > after the [me (SMTP) relay.skynet.be (ESMTP) googlegroups.com (SMTP) > gmail.com (POP3) me] round-trip it comes back in quoted-printable UTF-8 > as =C5=9B (equal Charlie Pantafayf equal Noveniner Bravo) which means > U+015B SMALL LATIN LETTER S WITH ACUTE instead of the 0xB6 (U+00B6 > PILCROW MARK) which I had sent. Ah, why couldn't Google simply > understand that Latin1 0xB6 means UTF-8 U+00B6? You don't need iconv to > know that. Ah, Google pisses me off. >:-( > > Best regards, > Tony.
signature.asc
Description: This is a digitally signed message part.
