Re: Word boundry would not work when using some wierd Unicode chars with the 'contained' syntax

On Sunday, February 8, 2015 at 11:31:48 AM UTC+8, Ben Fritz wrote:
> On Saturday, February 7, 2015 at 3:16:21 PM UTC-6, Jacky Liu wrote:
> > Here is the VimL code I wrote:
> >
> > " Use some wierd Unicode chars to mark the region, '+' being put here as a contrast.
> > syntax region myCmdLine matchgroup=myCmdLine_ start=/[⣱+]/ end=/[⡇⡗⡧+]/
> > hi link myCmdLine _LightGreen_233b5a
> > hi link myCmdLine_ Normal
> >
> > syntax keyword myCmdName man bind less containedin=myCmdLine contained
> > hi link myCmdName _Green_233b5a
> >
> > And here's its effect on some simple demonstrating text (see attached image file)
> >
> > With '+' as the marker all three syntax keywords were correctlly recognized, but not with the abnormal Unicode chars
> >
> > Another thing is using '*' to do a quick search would work normally, as would do the following search command:
> >
> > /\<man\|bind\|less\>
> >
> > 'iskeyword' or 'regexpengine' option seems have no effect here.
> >
> > Should this be considered a bug?
>
>
> Try it again, with an appropriate scriptencoding command in the file, to tell Vim how to interpret the bytes in the file.



OK, I added a modeline to my text file to tell Vim the fileencoding specifically:

/* Vim: set fileencoding=utf-8: */
/* Vim: set tabstop=4: */

⣱man bind | less⡇

+man bind | less+

the 'tabstop' option was there to make sure the modeline works. the result seems to have no defference.

For your reference: The underlying fileencoding in respect of my daily usage of Vim was almost always utf-8.

All the best ~









--
--
You received this message from the "vim_use" 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_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.