Tony Mechelynck wrote: > In a custom 'statusline', items %b or %B mean the current character, not > necessarily the current byte. For instance, if 'encoding' is UTF-8, the > status line string > > U+%04B > > will display the Unicode codepoint under the cursor according to the > usual conventions: U+ 4 hex digits in the BMP (U+0000 to U+FFFF), or U+ > as many hex digits as necessary (normally 5 or 6) outside the BMP (i.e. > U+10000 and higher — the Unicode Consortium currently allows codepoints > up to U+10FFFD, where U+F0000 and higher, among others, are "for private > use"; Vim allows codepoints up to U+7FFFFFFF). Similarly with lowercase > b but in decimal (I just checked them both). > > See the attached proposed patch to options.txt. This patch was > constructed according to the "traditional Vim" patching conventions (to > apply it, start at the parent of runtime/ src/ etc., patch using -p0, > and non-unified context diff) rather than "Mercurial" patching > conventions (start at the same point but patch using -p1, and unified > context diff). > > I *think* that transmission via email will have converted all ends of > lines to "dos-style" (CR+LF rather than my usual "unix-style" LF) but > I'm not 100% sure.
Thanks, I'll include the change. I can just do cwcharacter<Esc> instead of figuring out how to patch :-). -- hundred-and-one symptoms of being an internet addict: 225. You sign up for free subscriptions for all the computer magazines /// 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
