search('multi-byte char', 'bce') does not match at cursor position.

2015-07-09 Fir de Conversatie Yukihiro Nakadaira
search('multi-byte char', 'bce') does not match at cursor position. Steps to reproduce: $ vim -u NONE :set encoding=utf-8 :call setline(1, \uff21) :echo search(\uff21, bceW) no wrap scan 0 Expected: 1 I think that the attached patch fixes this problem. Please check it. For

Possible bug: Unicode characters in [g]vim -S file name on Windows 8.1

2015-07-09 Fir de Conversatie ben
Not sure if this is the right place to report a bug, but here it comes... How to reproduce: 1. Start Command Prompt. 2. Create an empty test directory anywhere and cd into it. 3. Create a subdirectory with a Unicode character in it, e.g. mkdir α 4. Create a file named Session.vim in the Unicode

Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'

2015-07-09 Fir de Conversatie vim
Comment #3 on issue 381 by h.east@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 This problem occurs in vim 7.4.757 to 7.4.765. (fixed by 7.4.766) If you use urxvt and using transparency, check below thread and

how to detect ins-completion mode?

2015-07-09 Fir de Conversatie Alex Efros
Hi! I'm trying to implement starting omni completion with Tab and then looping over completion variants also with Tab. I've map Tab to function which returns \c-x\c-o to start omni completion, but next Tab should return \c-n and I've no idea how to detect is user already in ins-completion mode.

Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'

2015-07-09 Fir de Conversatie vim
Comment #2 on issue 381 by odabr...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 I cannot reproduce this. File test.vim contains set nocompatible Testing with vim -u test.vim -U NONE --noplugin test.vim

Re: [patch] Respect file's EOL/NOEOL settings

2015-07-09 Fir de Conversatie Olaf Dabrunz
On 08-Jul-15, Pavel Samarkin wrote: Hi, If you use git, then in “git help attributes” the example mentioning *.vcproj files might be useful for you. Possibly the end-of-line normalization offered by git includes the case where just the last line needs normalization. Roland -

Re: Patch 7.4.757

2015-07-09 Fir de Conversatie Bram Moolenaar
Hirohito Higashi wrote: Hi Bram and list! 2015-7-9(Thu) 10:47:12 UTC+9 h_east: Hi Bram! 2015-7-9(Thu) 4:55:17 UTC+9 Bram Moolenaar: Hirohito Higashi wrote: 2015-7-8(Wed) 2:08:03 UTC+9 Bram Moolenaar: Hirohito Higashi wrote: Hi Bram, Anatol and Vim

Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'

2015-07-09 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 381 by expro...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 What steps will reproduce the problem? 1. find a text file with non-empty first

Re: Issue 381 in vim: 'nocompatible' in vimrc causes the first char changed to 'g'

2015-07-09 Fir de Conversatie vim
Comment #1 on issue 381 by expro...@gmail.com: 'nocompatible' in vimrc causes the first char changed to 'g' https://code.google.com/p/vim/issues/detail?id=381 correction: - The first char of first line of **the buffer** will always be 'g' regardless what the file contains. -- You

Re: Possible bug: Unicode characters in [g]vim -S file name on Windows 8.1

2015-07-09 Fir de Conversatie Nikolay Pavlov
2015-07-09 6:47 GMT+03:00 ben bgol...@gmail.com: Not sure if this is the right place to report a bug, but here it comes... How to reproduce: 1. Start Command Prompt. 2. Create an empty test directory anywhere and cd into it. 3. Create a subdirectory with a Unicode character in it, e.g.

Re: Patch 7.4.757

2015-07-09 Fir de Conversatie h_east
Hi Bram, 2015-7-9(Thu) 18:30:55 UTC+9 Bram Moolenaar: Hirohito Higashi wrote: Hi Bram and list! 2015-7-9(Thu) 10:47:12 UTC+9 h_east: Hi Bram! 2015-7-9(Thu) 4:55:17 UTC+9 Bram Moolenaar: Hirohito Higashi wrote: 2015-7-8(Wed) 2:08:03 UTC+9 Bram Moolenaar: