Re: Test failure on OS X

On 2015/01/29, at 6:39, Bram Moolenaar wrote: > It's better to not skip the test. Can you try if it works by using > "unnamed" instead of "unnamedplus" and then using the * register instead > of +? The * register should work everywhere. Yes. The test succeeds (and is not skipped) on my Mac wit

count for zr and zm (patch)

Hi Bram, I attach a small patch which adds count for zr and zm normal commands. It also adds a check to not go beyond the maximal fold level with zr. Best regards, Marcin -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are reply

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

Updates: Labels: patch Comment #1 on issue 324 by chrisbr...@googlemail.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 Here is a patch. I even added a test, but unfortunately, undo works slightly diff

Re: Issue 319 in vim: New option to not beep with 'showmatch'

Hi Bram! On Mi, 28 Jan 2015, Bram Moolenaar wrote: > > Christian wrote: > > > Updates: > > Labels: patch > > > > Comment #10 on issue 319 by chrisbr...@googlemail.com: New option to not > > beep with 'showmatch' > > https://code.google.com/p/vim/issues/detail?id=319 > > > > Here is a pa

Re: Test failure on OS X

Jun Takimoto wrote: > On 2015/01/28, at 11:33, Manuel Ortega wrote: > > Test results: > > test_eval FAILED > > The failure is in the section '{{{1 System clipboard'. > > There is only one clipboard on Mac OS X, and it seems > both "* and "+ refer to it. For example both > "*yyand

Re: Issue 319 in vim: New option to not beep with 'showmatch'

Christian wrote: > Updates: > Labels: patch > > Comment #10 on issue 319 by chrisbr...@googlemail.com: New option to not > beep with 'showmatch' > https://code.google.com/p/vim/issues/detail?id=319 > > Here is a patch, that implements the 'bellon' option. If anybody has a > better nam

Re: [patch] "autocmd Foo " does not work

Lech Lorens wrote: > Vim incorrectly reads the number of buffer for which an autocommand > should be registered. The attached patch fixes the problem. Thanks! -- hundred-and-one symptoms of being an internet addict: 137. You decide to stay in college for an additional year or two, just

Re: Patch 7.4.601

Christian Brabandt wrote: > Hi Bram! > > On Di, 27 Jan 2015, Bram Moolenaar wrote: > > > > > Patch 7.4.601 > > Problem:It is not possible to have feedkeys() insert characters. > > Solution: Add the 'i' flag. > > Files: src/eval.c, runtime/doc/eval.txt > > Let's add a test for t

Re: Test failure on OS X

On Wed, Jan 28, 2015 at 3:07 AM, Kazunobu Kuriyama < kazunobu.kuriy...@nifty.com> wrote: > Hi, > > On Jan 28, 2015, at 11:33, Manuel Ortega wrote: > > Sorry if this is a repeat of something already known. On OS X 10.10.1, > Vim 7.4.608 will have "make test" fail: > > Test results: > test_eval FA

Re: Issue 323 in vim: setreg(..., ..., 'al') keeps appending newlines

Comment #2 on issue 323 by nicolash...@gmail.com: setreg(..., ..., 'al') keeps appending newlines https://code.google.com/p/vim/issues/detail?id=323 At first I thought this solution might not be sufficiently general. Yet, trying to come up with other cases where I wouldn't want a newline to

Re: Issue 323 in vim: setreg(..., ..., 'al') keeps appending newlines

Updates: Labels: patch Comment #1 on issue 323 by chrisbr...@googlemail.com: setreg(..., ..., 'al') keeps appending newlines https://code.google.com/p/vim/issues/detail?id=323 Here is a patch, that adds some tests. Since the test_eval.ok file makes diff create a binary patch file, o

writable '=' register

Hi, :h quote= states: , | 6. Expression register "= *quote_=* *quote=* *@=* | This is not really a register that stores text, but is a way to use an | expression in commands which use a register. The expression register is | read-only; you cannot put text into it. After t

Re: DirDiff plugin broken by 7.4.565

On 2015-01-28, Xavier de Gaye wrote: > On 01/27/2015 01:29 PM, Bram Moolenaar wrote: > > > > Xavier de Gaye wrote: > > > >> Running the DirDiff plugin with the latest 7.4.592 produces the following > >> error message: > >> > >> E16: Invalid range: 3wincmd > >> > >> This occurs since 7.4.565.

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

Status: New Owner: Labels: Type-Defect Priority-Medium New issue 324 by paoe...@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 What steps will reproduce the problem? While somewhat elaborate, this

Re: [patch] add function: colorschemes()

Great, thanks Christian. Then forget the patch. On Wednesday, January 28, 2015 at 10:44:48 PM UTC+8, Christian Brabandt wrote: > Am 2015-01-28 15:35, schrieb Brook Hong: > > I want to get a list of all installed color schemes when I am trying > > to change color scheme automatically. > > The func

Re: [patch] add function: colorschemes()

Am 2015-01-28 15:35, schrieb Brook Hong: I want to get a list of all installed color schemes when I am trying to change color scheme automatically. The function returns a list of all color schemes Patch attached. Well, thanks for contributing. But... You could simply use :echo globpath(&rtp,

Re: [patch] "autocmd Foo " does not work

On 27 January 2015, Lech Lorens wrote: > Vim incorrectly reads the number of buffer for which an autocommand > should be registered. The attached patch fixes the problem. +1 /lcd -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the t

Re: [patch] add function: colorschemes()

On Jan 28, 2015 9:35 AM, "Brook Hong" wrote: > > I want to get a list of all installed color schemes when I am trying to change color scheme automatically. > The function returns a list of all color schemes > > Patch attached. > Why not a more generalized way to list any type of plugin? plugins(

[patch] add function: colorschemes()

I want to get a list of all installed color schemes when I am trying to change color scheme automatically. The function returns a list of all color schemes Patch attached. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are reply

Re: DirDiff plugin broken by 7.4.565

On 01/27/2015 01:29 PM, Bram Moolenaar wrote: > > Xavier de Gaye wrote: > >> Running the DirDiff plugin with the latest 7.4.592 produces the following error message: >> >> E16: Invalid range: 3wincmd >> >> This occurs since 7.4.565. >> There are other related reports, for example the thread

Re: Test failure on OS X

On 2015/01/28, at 11:33, Manuel Ortega wrote: > Test results: > test_eval FAILED The failure is in the section '{{{1 System clipboard'. There is only one clipboard on Mac OS X, and it seems both "* and "+ refer to it. For example both "*yyand "+yy yank the current line to the cl

Re: Test failure on OS X

Hi,On Jan 28, 2015, at 11:33, Manuel Ortega wrote:Sorry if this is a repeat of something already known.  On OS X 10.10.1, Vim 7.4.608 will have "make test" fail:Test results:test_eval FAILEDTEST FAILUREmake[2]: *** [report] Error 1make[1]: *** [test] Error 2make: *** [test]