Re: Capture columns nummers of matches ending with double byte chars

Ken Takata wrote: > (Cc-ing to vim_dev) > > Hi, > > 2016/4/26 Tue 15:00:33 UTC+9 rameo wrote: > > > > > > It is much better to download sources from https://github.com/vim/vim. > > > > > > > Found it: > > https://github.com/vim/vim-win32-installer/releases > > > > However... > > Tried: > >

Re: Capture columns nummers of matches ending with double byte chars

(Cc-ing to vim_dev) Hi, 2016/4/26 Tue 15:00:33 UTC+9 rameo wrote: > > > > It is much better to download sources from https://github.com/vim/vim. > > > > Found it: > https://github.com/vim/vim-win32-installer/releases > > However... > Tried: > gvim_7.4.1782_x86.exe > gvim_7.4.1786_x86.exe >

Re: Capture columns nummers of matches ending with double byte chars

Op dinsdag 26 april 2016 09:14:52 UTC+2 schreef rameo: > Op dinsdag 26 april 2016 08:14:33 UTC+2 schreef Christian Brabandt: > > Hi rameo! > > > > On Mo, 25 Apr 2016, rameo wrote: > > > > > > > > > > > > > It is much better to download sources from https://github.com/vim/vim. > > > > > > > >

Re: Capture columns nummers of matches ending with double byte chars

Op dinsdag 26 april 2016 08:14:33 UTC+2 schreef Christian Brabandt: > Hi rameo! > > On Mo, 25 Apr 2016, rameo wrote: > > > > > > > > > It is much better to download sources from https://github.com/vim/vim. > > > > > > > Found it: > > https://github.com/vim/vim-win32-installer/releases > > >

Re: Capture columns nummers of matches ending with double byte chars

Hi rameo! On Mo, 25 Apr 2016, rameo wrote: > > > > > It is much better to download sources from https://github.com/vim/vim. > > > > Found it: > https://github.com/vim/vim-win32-installer/releases > > However... > Tried: > gvim_7.4.1782_x86.exe > gvim_7.4.1786_x86.exe > > Both gives an

Re: Capture columns nummers of matches ending with double byte chars

> > It is much better to download sources from https://github.com/vim/vim. > Found it: https://github.com/vim/vim-win32-installer/releases However... Tried: gvim_7.4.1782_x86.exe gvim_7.4.1786_x86.exe Both gives an error: Error detected while processing vimrc_example.vim line 114: E919:

Re: Capture columns nummers of matches ending with double byte chars

2016-04-26 0:45 GMT+03:00 rameo : > Op maandag 25 april 2016 22:26:27 UTC+2 schreef Ken Takata: >> Hi rameo, >> >> 2016/4/23 Sat 21:37:15 UTC+9 rameo wrote: >> > Searchpos() doesn't return the right end value of a match if the match end >> > with a double byte character

Re: Capture columns nummers of matches ending with double byte chars

Op maandag 25 april 2016 22:26:27 UTC+2 schreef Ken Takata: > Hi rameo, > > 2016/4/23 Sat 21:37:15 UTC+9 rameo wrote: > > Searchpos() doesn't return the right end value of a match if the match end > > with a double byte character (èéòìùá...). (encoding utf-8) > > Isn't this a bug > > You

Re: Capture columns nummers of matches ending with double byte chars

Hi rameo, 2016/4/23 Sat 21:37:15 UTC+9 rameo wrote: > Searchpos() doesn't return the right end value of a match if the match end > with a double byte character (èéòìùá...). (encoding utf-8) > Isn't this a bug You might misunderstand the spec of searchpos(). When the 'e' flag is specified,

Re: Capture columns nummers of matches ending with double byte chars

2016-04-21 22:03 GMT+03:00 rameo : > Since I use Vim I have troubles with double byte characters. > > I want to capture all strings of matches together with startcolumn and > endcolumn of a match (line by line). I don't need only the strings but also > the columnnumbers for

Re: Capture columns nummers of matches ending with double byte chars

Searchpos() doesn't return the right end value of a match if the match end with a double byte character (èéòìùá...). (encoding utf-8) Isn't this a bug Would it be possible to add a feature in Vim like finditer in Python? Searchpos() searches the entire file till stopline. finditer returns

Capture columns nummers of matches ending with double byte chars

Since I use Vim I have troubles with double byte characters. I want to capture all strings of matches together with startcolumn and endcolumn of a match (line by line). I don't need only the strings but also the columnnumbers for other functions. The last few years I used match/matchend then I