Re: completion break dot register

Yasuhiro Matsumoto wrote: > Hi list. > > $ cat < test.vim > set nocompatible > > call append(1, 'aa11') > call append(1, 'aa11') > > inoremap =ListMonths() > > func! ListMonths() > call complete(1, ['January', 'February', 'March', > \ 'April', 'May', 'June', 'July', 'August', 'Sept

Patch 7.4.630

Patch 7.4.630 Problem:When using Insert mode completion combined with autocommands the redo command may not work. Solution: Do not save the redo buffer when executing autocommands. (Yasuhiro Matsumoto) Files: src/fileio.c *** ../vim-7.4.629/src/fileio.c 2015-01

Patch 7.4.631

Patch 7.4.631 Problem:The default conceal character is documented to be a space but it's initially a dash. (Christian Brabandt) Solution: Make the intial value a space. Files: src/globals.h *** ../vim-7.4.630/src/globals.h2015-01-27 18:43:42.134535513 +0100 --- src

Re: concealing works differently than documented

Christian Brabandt wrote: > Bram, > consider this: > vim -u NONE -N ~/.vim/vimrc > :syn on > :set conceallevel=1 concealcursor=n > :syn match MyConceal /s/ containedin=ALL conceal > > Note, that the 's' will be set to '-'. > This is different than expected: > > ,[ :h 'conceallevel' ]- > |

Re: [Patch] Named marks can be lost after delete-undo-redo

Olaf Dabrunz wrote: > On 15-Feb-15, Bram Moolenaar wrote: > > If you have some time, it's always good to have a test that checks the > > problem is fixed. > > This did not seem to fit well into any existing test. So I wrote a > test_marks.in, which can also be a place to add more tests for marks

Re: completion break dot register

> Thanks. However, the call to restoreRedobuff() should then also be > skipped, otherwise the count for save_level will be off. I'll make > that work. No, it's doesn't fix this problem. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the te

Patch 7.4.632

Patch 7.4.632 (after 7.4.592) Problem:7.4.592 breaks the netrw plugin, because the autocommands are skipped. Solution: Roll back the change. Files: src/ex_cmds.c *** ../vim-7.4.631/src/ex_cmds.c2015-01-27 13:33:18.737649629 +0100 --- src/ex_cmds.c 2015-02-17

Re: completion break dot register

Yasuhiro Matsumoto wrote: > > Thanks. However, the call to restoreRedobuff() should then also be > > skipped, otherwise the count for save_level will be off. I'll make > > that work. > > No, it's doesn't fix this problem. Hmm, that isn't right. The calls to save and restore must be symmetri

Patch 7.4.633

Patch 7.4.633 Problem:After 7.4.630 the problem persists. Solution: Also skip redo when calling a user function. Files: src/eval.c *** ../vim-7.4.632/src/eval.c 2015-02-04 23:06:39.453536117 +0100 --- src/eval.c 2015-02-17 12:37:35.321823749 +0100 *** *** 8693,8705

Re: completion break dot register

Fixed in 7.4.633. Thank you. -- -- 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://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Grou

Patch 7.4.634

Patch 7.4.634 Problem:Marks are not restored after redo + undo. Solution: Fix the way marks are restored. (Olaf Dabrunz) Files: src/undo.c, src/testdir/Make_amiga.mak, src/testdir/Make_dos.mak, src/testdir/Make_ming.mak, src/testdir/Make_os2.mak, src/testdir/Make

Patch 7.4.635

Patch 7.4.635 Problem:If no NL or CR is found in the first block of a file then the 'fileformat' may be set to "mac". (Issue 77) Solution: Check if a CR was found. (eswald) Files: src/fileio.c *** ../vim-7.4.634/src/fileio.c 2015-02-17 10:58:20.479298803 +0100 --- src/file

Re: Patch 7.4.634

Hi Bram, 2015/2/17 Tue 21:44:04 UTC+9 Bram Moolenaar wrote: > Patch 7.4.634 > Problem:Marks are not restored after redo + undo. > Solution: Fix the way marks are restored. (Olaf Dabrunz) > Files:src/undo.c, src/testdir/Make_amiga.mak, > src/testdir/Make_dos.mak, > src/

Patch 7.4.636

Patch 7.4.636 Problem:A search with end offset gets stuck at end of file. (Gary Johnson) Solution: When a search doesn't move the cursor repeat it with a higher count. (Christian Brabandt) Files: src/normal.c, src/testdir/test44.in, src/testdir/test44.ok *** ../vim-7.4.635

Re: Patch 7.4.634

Ken Takata wrote: > Hi Bram, > > 2015/2/17 Tue 21:44:04 UTC+9 Bram Moolenaar wrote: > > Patch 7.4.634 > > Problem:Marks are not restored after redo + undo. > > Solution: Fix the way marks are restored. (Olaf Dabrunz) > > Files: src/undo.c, src/testdir/Make_amiga.mak, > > src/test

Patch 7.4.637

Patch 7.4.637 Problem:Incorrectly read the number of buffer for which an autocommand should be registered. Solution: Reverse check for "". (Lech Lorens) Files: src/fileio.c *** ../vim-7.4.636/src/fileio.c 2015-02-17 14:15:13.005523167 +0100 --- src/fileio.c2015-02

Patch 7.4.638

Patch 7.4.638 Problem:Can't build with Lua 5.3 on Windows. Solution: use luaL_optinteger() instead of LuaL_optlong(). (Ken Takata) Files: src/if_lua.c *** ../vim-7.4.637/src/if_lua.c 2015-02-04 23:07:55.928517161 +0100 --- src/if_lua.c2015-02-17 16:26:47.003111497 +0100 **

Re: Issue 77 in vim: [patch] Non-empty file without EOL markers should use default fileformat instead of mac.

Updates: Status: Fixed Comment #5 on issue 77 by chrisbr...@googlemail.com: [patch] Non-empty file without EOL markers should use default fileformat instead of mac. https://code.google.com/p/vim/issues/detail?id=77 included and Fixed by 7.4.635 -- You received this message because th

Re: Issue 329 in vim: Vim doesn't compile with Lua 5.3 on windows

Updates: Status: Fixed Comment #5 on issue 329 by chrisbr...@googlemail.com: Vim doesn't compile with Lua 5.3 on windows https://code.google.com/p/vim/issues/detail?id=329 Fixed by 7.4.638 -- You received this message because this project is configured to send all issue notificatio

Vim charity: financial report 2014

Hello Vim users, Vim users are asked to support a project in Uganda, and many have sent money in 2014. The ICCF foundation takes care of this and the financial report is now available: http://www.iccf.nl/jaarrekening2014en.pdf Also available in Dutch: http://www.iccf.nl/jaarrekening2014nl.pdf I

Re: linebreak and conceal display problems

Hi Ben! On Mo, 16 Feb 2015, Ben Fritz wrote: > On Monday, February 16, 2015 at 11:30:05 AM UTC-6, Ben Fritz wrote: > > On Friday, February 13, 2015 at 4:03:48 PM UTC-6, Christian Brabandt wrote: > > > > > > Finally, I could debug this. Here is the patch, including a test. > > > > > > > I confi

Re: Issue 332 in vim: `colorcolumn` adds trailing whitespace to any multiline copy-pasted content

Comment #2 on issue 332 by chrisbr...@googlemail.com: `colorcolumn` adds trailing whitespace to any multiline copy-pasted content https://code.google.com/p/vim/issues/detail?id=332 I can't seem to reproduce this. Please be more specific how you are copy-pasting. -- You received this messa

Re: Ctrl_L behave like Ctrl_P while pum_visible.

Hi Bram, 2015/2/9(Mon) 2:21:55 UTC+9 h_east: > Hi Bram and Nice Vim developers, > > 2015/1/6(Tue) 4:58:27 UTC+9 Bram Moolenaar: > > Yasuhiro Matsumoto wrote: > > > > > bug.vim > > > --- > > > set nocompatible > > > > > > inoremap =ListMonths() > > > > > > func! ListMonths() >

Patch 7.4.639

Patch 7.4.639 Problem:Combination of linebreak and conceal doesn't work well. Solution: Fix the display problems. (Christian Brabandt) Files: src/screen.c, src/testdir/test88.in, src/testdir/test88.ok, src/testdir/test_listlbr_utf8.in, src/testdir/test_listlbr_utf8.ok ***

Re: Ctrl_L behave like Ctrl_P while pum_visible.

Hirohito Higashi wrote: > 2015/2/9(Mon) 2:21:55 UTC+9 h_east: > > Hi Bram and Nice Vim developers, > > > > 2015/1/6(Tue) 4:58:27 UTC+9 Bram Moolenaar: > > > Yasuhiro Matsumoto wrote: > > > > > > > bug.vim > > > > --- > > > > set nocompatible > > > > > > > > inoremap =ListMonth

Patch 7.4.640

Patch 7.4.640 Problem:After deleting characters in Insert mode such that lines are joined undo does not work properly. (issue 324) Solution: Use Insstart instead of Insstart_orig. (Christian Brabandt) Files: src/edit.c *** ../vim-7.4.639/src/edit.c 2015-01-22 22:40:16.34

Re: Issue 324 in vim: Undo can leave buffer in a never before seen state after a multi-line edit.

Updates: Status: Fixed Comment #3 on issue 324 by brammool...@gmail.com: Undo can leave buffer in a never before seen state after a multi-line edit. https://code.google.com/p/vim/issues/detail?id=324 Fix included by patch 7.4.640 -- You received this message because this project is c

Re: linebreak and conceal display problems

On Tuesday, February 17, 2015 at 9:54:00 AM UTC-6, Christian Brabandt wrote: > Hi Ben! > > On Mo, 16 Feb 2015, Ben Fritz wrote: > > > On Monday, February 16, 2015 at 11:30:05 AM UTC-6, Ben Fritz wrote: > > > On Friday, February 13, 2015 at 4:03:48 PM UTC-6, Christian Brabandt > > > wrote: > > >

Re: concealing works differently than documented

On Di, 17 Feb 2015, Bram Moolenaar wrote: > Considering that resetting the listchars to its default does get you a > space, we need to fix the initial value. I'll make a patch Thanks. That makes my next patch easier. > (it's easy, I'll leave the difficult stuff to you :-). That's fine. As long

Re: Issue 77 in vim: [patch] Non-empty file without EOL markers should use default fileformat instead of mac.

Comment #6 on issue 77 by esw...@gmail.com: [patch] Non-empty file without EOL markers should use default fileformat instead of mac. https://code.google.com/p/vim/issues/detail?id=77 Moving the try_mac reset to inside the for loop seems to defeat its purpose, making mac format (nearly) impo

Re: [patch] Problem with syntax highlighting and "skipwhite"

On Mi, 05 Nov 2014, Bram Moolenaar wrote: > > this problem is not mentioned in the latest todo list. Is that no issue > > for your? > > As I already mentioned: It might break some things. > > The flag does apply to "nextgroup", as documented. That's why it checks > current_next_flags. > > Als