Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-14 Fir de Conversatie Tony Mechelynck
On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote: Oops. sorry. However, the problem happen with the script as your said. :-) Thanks. E486: Pattern not found means that there was no match. Are you sure you ran that script while the current file contained one or more 。 characters? When I do

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-14 Fir de Conversatie Dominique Pelle
2009/1/14 Tony Mechelynck antoine.mechely...@gmail.com: On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote: Oops. sorry. However, the problem happen with the script as your said. :-) Thanks. E486: Pattern not found means that there was no match. Are you sure you ran that script while the

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-14 Fir de Conversatie Tony Mechelynck
On 14/01/09 09:54, Dominique Pelle wrote: 2009/1/14 Tony Mechelynckantoine.mechely...@gmail.com: On 14/01/09 07:16, Yasuhiro MATSUMOTO wrote: Oops. sorry. However, the problem happen with the script as your said. :-) Thanks. E486: Pattern not found means that there was no match. Are

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-14 Fir de Conversatie Yasuhiro MATSUMOTO
Bram, please check third patch from me. :-) see below as descriptions. http://groups.google.co.jp/group/vim_dev/browse_thread/thread/e9945dbdd6ab388f?hl=ja#455ac73ba4bb0e47 - Yasuhiro Matsumoto On Wed, Jan 14, 2009 at 6:00 PM, Tony Mechelynck antoine.mechely...@gmail.com wrote: On 14/01/09

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-14 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: Bram, please check third patch from me. :-) see below as descriptions. http://groups.google.co.jp/group/vim_dev/browse_thread/thread/e9945dbdd6ab388f?hl=ja#455ac73ba4bb0e47 Thanks, I'll add it to the todo list. -- Engineers understand that their appearance

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Yasuhiro MATSUMOTO
oops. the patch have a bug. please check following. Index: src/term.c === --- src/term.c (revision 1318) +++ src/term.c (working copy) @@ -5152,7 +5152,7 @@ #ifdef FEAT_MBYTE /* skip multibyte char correctly */ -

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Yasuhiro MATSUMOTO
Hmm. I broke CUI mode. Index: src/term.c === --- src/term.c (revision 1318) +++ src/term.c (working copy) @@ -5152,7 +5152,7 @@ #ifdef FEAT_MBYTE /* skip multibyte char correctly */ - for (i = (*mb_ptr2len)(src); i

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Bram Moolenaar
Yasuhiro Matsumoto wrote: Hi. bram and all. I found a bug about treating multi-byte and special characters in command line. ex: :set enc=utf-8 :command! SubJapanesePeriodToDot %s/。/./g 。 mean period in japanese utf-8. and it has 0x80 in leading byte. but replace_termcodes treat

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Tony Mechelynck
On 13/01/09 16:31, Bram Moolenaar wrote: Yasuhiro Matsumoto wrote: Hi. bram and all. I found a bug about treating multi-byte and special characters in command line. ex: :set enc=utf-8 :command! SubJapanesePeriodToDot %s/。/./g 。 mean period in japanese utf-8. and it has 0x80

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Yasuhiro MATSUMOTO
Hi, Tony. Yes it's full width full stop character in utf-8. and it include 0x80. E38082 i.e. :command! SubJapanesePeriodToDot %s/。/./g :SubJapanesePeriodToDot I get an error E486: Pattern not found. Please check attached script. On Wed, Jan 14, 2009 at 1:46 AM, Tony Mechelynck

Re: some multi-byte is treated as K_SPECIAL in command line

2009-01-13 Fir de Conversatie Yasuhiro MATSUMOTO
Oops. sorry. However, the problem happen with the script as your said. :-) Thanks. On Wed, Jan 14, 2009 at 2:03 PM, Tony Mechelynck antoine.mechely...@gmail.com wrote: On 14/01/09 01:18, Yasuhiro MATSUMOTO wrote: Hi, Tony. Yes it's full width full stop character in utf-8. and it