Yasuhiro Matsumoto wrote:

> > > On Sunday, March 20, 2016 at 11:14:50 PM UTC+9, Elimar Riesebieter wrote:
> > > > * Bram Moolenaar <b...@moolenaar.net> [2016-03-19 18:42 +0100]:
> > > > 
> > > > > 
> > > > > Patch 7.4.1604
> > > > > Problem:    Although emoji characters are ambiguous width, best is to 
> > > > > treat
> > > > >             them as full width.
> > > > > Solution:   Update the Unicode character tables. Add the 'emoji' 
> > > > > options.
> > > > >             (Yasuhiro Matsumoto)
> > > > > Files:      runtime/doc/options.txt, runtime/optwin.vim,
> > > > >             runtime/tools/unicode.vim, src/mbyte.c, src/option.c, 
> > > > > src/option.h
> > > > 
> > > > This patch introduced:
> > > > 
> > > > E474: Invalid argument: listchars=tab:▶\ 
> > > > ,trail:_,extends:>,precedes:<,eol:¬
> > > > 
> > > > encoding is set to utf8. 
> > > > set noemoji doesn't help.
> > > > 
> > > > Seen at starting vim from commandline either in xterm or in linux
> > > > console.
> > > > 
> > > > Elimar
> > > > -- 
> > > >   The path to source is always uphill!
> > > >                                 -unknown-
> > > 
> > > If you want to set ▶ into listchars, you need to set noemoji before set 
> > > listchars.
> > 
> > Hmm, this character is both in emoji and ambiguous tables.
> > It doesn't look like an emoji character to me.
> > Should we perhaps drop the characters from the emoji table if they are
> > already in the ambiguous table?
> > 
> > I also notice that in the emoji table contiguous ranges need to be
> > merged:
> > 
> >     {0x1f5fb, 0x1f5ff},
> >     {0x1f600, 0x1f600},
> >     {0x1f601, 0x1f610},
> >     {0x1f611, 0x1f611},
> >     {0x1f612, 0x1f614},
> >     {0x1f615, 0x1f615},
> >     {0x1f616, 0x1f616},
> >     {0x1f617, 0x1f617},
> >     {0x1f618, 0x1f618},
> >     {0x1f619, 0x1f619},
> >     {0x1f61a, 0x1f61a},
> >     {0x1f61b, 0x1f61b},
> >     {0x1f61c, 0x1f61e},
> >     {0x1f61f, 0x1f61f},
> >     {0x1f620, 0x1f625},
> >     {0x1f626, 0x1f627},
> >     {0x1f628, 0x1f62b},
> >     {0x1f62c, 0x1f62c},
> >     {0x1f62d, 0x1f62d},
> >     {0x1f62e, 0x1f62f},
> >     {0x1f630, 0x1f633},
> >     {0x1f634, 0x1f634},
> >     {0x1f635, 0x1f640},
> > 
> > This should be:
> >     {0x1f5fb, 0x1f640},
> 
> This is a patch to merge it.
> 
> https://gist.github.com/mattn/5300623003d6d2c4563d

Thanks.  I'll see if I can also remove the ambigious characters.

-- 
The primary purpose of the DATA statement is to give names to constants;
instead of referring to pi as 3.141592653589793 at every appearance, the
variable PI can be given that value with a DATA statement and used instead
of the longer form of the constant.  This also simplifies modifying the
program, should the value of pi change.
        -- FORTRAN manual for Xerox Computers

 /// Bram Moolenaar -- b...@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    ///

-- 
-- 
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 vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui