Re: Issue in match() function with multi-byte characters

On 30/03/14 10:53, Andre Sihera wrote: > szLine = "今日時間日 本語勉強 思今日は２時間ぐらい日本語を勉 強したい > と思います。" > Somehow, an extra whitespace crept into my example line as it got sent. It should read: szLine = "今日時間日本語勉強 思今日は２時間ぐらい日本語を勉強したいと思 いま す。" (P.S. If it comes out wrong this time as well then it's a bug in

Re: Issue in match() function with multi-byte characters

On 30/03/14 09:03, Nikolay Pavlov wrote: On Mar 30, 2014 3:35 AM, "Dmitry Frank" > wrote: > > Hello all. > > match() function returns index of first match, but if there are multi-byte chars before first match, then each multi-byte chars is interpreted as severa

back- and forwardslash Inconsistency for viminfo

Under Windows, the undo-, backup- and swapdir-settings accept back- or forward-slashes, but viminfo only the backslash variant. -- -- 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://ww

Re: German Spellfile Session management

Am Freitag, 28. März 2014 23:31:51 UTC+1 schrieb enno@gmail.com: > When restoring a session with spelllang=de, encoding = utf-8 and a nonempty > german spellfile de.utf-8.add , the de.utf-8.spl is not read. > > This problem does not occur when > > - set spell spelllang=de is invoked manual

Re: Issue in match() function with multi-byte characters

Then, how can I get the symbol index (not byte offset) of a match? There is awesome plugin "PreciseJump": http://www.vim.org/scripts/script.php?script_id=3437 , it gets array of all symbols of the line, like that: let lines_with_markers[l] = split(getline(l), '\zs') So that here's symbol

Re: Issue in match() function with multi-byte characters

On Mar 30, 2014 3:35 AM, "Dmitry Frank" wrote: > > Hello all. > > match() function returns index of first match, but if there are multi-byte chars before first match, then each multi-byte chars is interpreted as several chars, so, index becomes wrong. > > Say, match("foobar", "bar") returns 3, whi

Re: Issue in match() function with multi-byte characters

2014-03-30 3:34 GMT+04:00 Dmitry Frank : > Hello all. > > match() function returns index of first match, but if there are multi-byte > chars before first match, then each multi-byte chars is interpreted as > several chars, so, index becomes wrong. > > Say, match("foobar", "bar") returns 3, which i

Issue in match() function with multi-byte characters

Hello all. match() function returns index of first match, but if there are multi-byte chars before first match, then each multi-byte chars is interpreted as several chars, so, index becomes wrong. Say, match("foobar", "bar") returns 3, which is correct. But match("яfoobar", "bar") returns 5, wh

Re: Issue 208 in vim: 'make' loops forever during normal compilation

Comment #2 on issue 208 by benhg...@gmail.com: 'make' loops forever during normal compilation http://code.google.com/p/vim/issues/detail?id=208 I did try it with make clean, and make distclean first as well. I don't think the make part should be checking dependencies as all right? That sh

Re: Patch 7.4.153

Hi, I had a report from nakinor that compiler warnings occur after 7.4.153. E.g.: In file included from if_python3.c:773: ./if_py_both.h:2331:27: warning: incompatible pointer types passing 'PySliceObject *' to parameter of type 'PyObject *' (aka 'struct _object *') [-Wincompatible-p

Page on developing Vim

I have asked Christian Brabandt to write down how he creates and maintains patches for Vim. You can read it here: http://www.vim.org/develop.php I hope this is useful. If you have suggestions to improve this page, please discuss here. -- A radioactive cat has eighteen half-lives. /// Bram

Re: Need help with understanding vimscript code snippet

On 29/03/14 11:40, Bruno Sutic wrote: Hi, I'm posting this to vim_dev because it is related to plugin development (apologies if it should go to vim_use). Recently, I discovered Tim Pope's vim-rsi plugin (https://github.com/tpope/vim-rsi). I was mind-blown to discover you can actually use Meta

Re: Change default viewdir on Windows to $HOME/vimfiles/view

Rob Owens wrote: > The default viewdir on Windows is $VIM/vimfiles/view, which is to say > C:\Program Files (x86)\Vim\vimfiles\view. When a user runs :mkview, Vim > attempts to write to the viewdir, but the user most likely does not have > write permission to this directory. The following error

Re: German Spellfile Session management

Enno Nagel wrote: > When restoring a session with spelllang=de, encoding = utf-8 and a > nonempty german spellfile de.utf-8.add , the de.utf-8.spl is not read. > > This problem does not occur when > > - set spell spelllang=de is invoked manually, > - for other languages. Tested for English an

Re: Issue 208 in vim: 'make' loops forever during normal compilation

Comment #1 on issue 208 by brammool...@gmail.com: 'make' loops forever during normal compilation http://code.google.com/p/vim/issues/detail?id=208 What was the situation before you started? Did you do "make distclean" first? Did you start with a clean setup or did you build before? How did yo

Need help with understanding vimscript code snippet

Hi, I'm posting this to vim_dev because it is related to plugin development (apologies if it should go to vim_use). Recently, I discovered Tim Pope's vim-rsi plugin (https://github.com/tpope/vim-rsi). I was mind-blown to discover you can actually use Meta (alt key) mappings in terminal vim. I t