Re: Patch 7.4.1963

Hi John, 2016/7/10 Sun 6:52:04 UTC+9 John Marriott wrote: > On 27-Jun-2016 4:38 AM, Bram Moolenaar wrote: > > Patch 7.4.1963 > > Problem:Running Win32 Vim in mintty does not work. > > Solution: Detect mintty and give a helpful error message. (Ken Takata) > > Files:

Re: Patch 7.4.1963

On 27-Jun-2016 4:38 AM, Bram Moolenaar wrote: Patch 7.4.1963 Problem:Running Win32 Vim in mintty does not work. Solution: Detect mintty and give a helpful error message. (Ken Takata) Files: src/Make_cyg_ming.mak, src/Make_mvc.mak, src/iscygpty.c, src/iscygpty.h,

Patch 7.4.2015

Patch 7.4.2015 Problem:When a file gets a name when writing it 'acd' is not effective. (Dan Church) Solution: Invoke DO_AUTOCHDIR after writing the file. (Allen Haim, closes #777, closes #803) Add test_autochdir() to enable 'acd' before "starting" is

Patch 7.4.2014

Patch 7.4.2014 Problem:Using "noinsert" in 'completeopt' does not insert match. Solution: Set compl_enter_selects. (Shougo, closes #875) Files: src/edit.c, src/testdir/test_popup.vim *** ../vim-7.4.2013/src/edit.c 2016-07-09 21:48:59.702071022 +0200 --- src/edit.c 2016-07-09

Patch 7.4.2013

Patch 7.4.2013 Problem:Using "noinsert" in 'completeopt' breaks redo. Solution: Set compl_curr_match. (Shougo, closes #874) Files: src/edit.c, src/testdir/test_popup.vim *** ../vim-7.4.2012/src/edit.c 2016-06-26 18:37:51.886998663 +0200 --- src/edit.c 2016-07-09 21:44:23.638200049

Re: Using file name with quickfix commands

On 9 July 2016, Bram Moolenaar wrote: > > Lcd wrote: > > > > > > > On 7 July 2016, Bram Moolenaar wrote: > > [...] > > > > > I don't understand. What does "access to a buffer" mean? > > > > > > > > Syntastic is a sort of generalised compiler set, it

Re: Using file name with quickfix commands

Lcd wrote: > > > > > On 7 July 2016, Bram Moolenaar wrote: > [...] > > > > I don't understand. What does "access to a buffer" mean? > > > > > > Syntastic is a sort of generalised compiler set, it runs > > > external compilers, and shows the results in a loclist. Except

Re: lambda again

Ken Takata wrote: [...] > > I do think that the backslash (or any other special character that might > > be available) makes it ugly. > > > > Although we can find the end of the expression without the "}", mistakes > > will be very hard to figure out. Also reading back a lambda that's > >

Re: Using file name with quickfix commands

On 9 July 2016, Bram Moolenaar wrote: > > Lcd wrote: > > > > > On 7 July 2016, Bram Moolenaar wrote: [...] > > > I don't understand. What does "access to a buffer" mean? > > > > Syntastic is a sort of generalised compiler set, it runs > > external

Re: Patch to add a function to get the command line completion matches

Hi Bram, On Sat, Jul 9, 2016 at 9:50 AM, Bram Moolenaar wrote: > > Yegappan wrote: > >> >> I am attaching a patch to add a function to get the command-line >> >> completion matches. >> > >> > Interesting. It seems useful, but I can't think of when or where. >> > How would

Re: [vim/vim] patch 7.4.2008 (79815f1)

Hi Bram, 2016-7-10(Sun) 3:07:33 UTC+9 Bram Moolenaar: > Hirohito Higashi wrote: > > > > > Perhaps, it would change leakage. > > > may change `evalcmd(` to `execute(`. > > > > What do you mean with "leakage"? It means ... Modification is required. But it has not been modified. thanks. --

Re: Version on www.vim.org is stuck at 7.4.1999

Christian Robinson wrote: > I just happened to notice that the patchlevel number isn't updating on > the website. I'm guessing an auto-update script has too low of an > upper boundary assumption. Thanks for the note. I suppose some script isn't prepared for such a large number of patches...

Re: Using file name with quickfix commands

Lcd wrote: > > > On 7 July 2016, Bram Moolenaar wrote: > > > > > > > > Christian Brabandt wrote: > > > > > > > > > On Do, 07 Jul 2016, Bram Moolenaar wrote: > > > > > > > > > > > > > > > > > There has been a request that when adding items to the > > > > > > quickfix list, no

Patch 7.4.2012

Patch 7.4.2012 (after 7.4.2011) Problem:Test for getcompletion() does not pass on all systems. Solution: Only test what is supported. Files: src/testdir/test_cmdline.vim *** ../vim-7.4.2011/src/testdir/test_cmdline.vim2016-07-09 18:49:47.202419946 +0200 ---

Re: A plea against the name "execute()"

> > call and call() are also. But I don't think it makes confusing. But it does, for new users and people learning VimScript. I'm not confused *anymore* about :substitute/substitute(), because I've now done a ton of vimscripting. But when I was new, I can't tell you how many times that messed

Re: [vim/vim] E36 from quickfix list (smaller than 3 lines) with noequalalways and buftype=nofile (#908)

On 9 July 2016, Dominique Pellé wrote: > LCD 47 wrote: > > > On 9 July 2016, Christian Brabandt wrote: > >> On Fr, 08 Jul 2016, LCD 47 wrote: > >> > >> > Not recent, but do you remember the problem introduced by > >> > 1640?

Re: Patch to add a function to get the command line completion matches

Yegappan wrote: > >> I am attaching a patch to add a function to get the command-line > >> completion matches. > > > > Interesting. It seems useful, but I can't think of when or where. > > How would one use this? > > > > Many Vim plugins need the list of matches produced by the built-in > Vim

Patch 7.4.2011

Patch 7.4.2011 Problem:It is not easy to get a list of command arguments. Solution: Add getcompletion(). (Yegappan Lakshmanan) Files: runtime/doc/eval.txt, src/eval.c, src/ex_docmd.c, src/proto/ex_docmd.pro, src/testdir/test_cmdline.vim ***

Re: [vim/vim] E36 from quickfix list (smaller than 3 lines) with noequalalways and buftype=nofile (#908)

LCD 47 wrote: > On 9 July 2016, Christian Brabandt wrote: >> On Fr, 08 Jul 2016, LCD 47 wrote: >> >> > Not recent, but do you remember the problem introduced by 1640? >> > It's still with us. _shrug_ >> >> I don't follow. That was a bugfix for a crash

Re: A plea against the name "execute()"

On Sunday, July 10, 2016 at 1:35:22 AM UTC+9, Manuel Ortega wrote: > I don't have positive suggestion for an alternative, but... > > > Please, please don't name the new function "execute()".  It only breeds > confusion because there is already a command called "execute".  It really > sucks

A plea against the name "execute()"

I don't have positive suggestion for an alternative, but... Please, please don't name the new function "execute()". It only breeds confusion because there is already a command called "execute". It really sucks when this happens, like with substitute() and :substitute. New users get confused,

Version on www.vim.org is stuck at 7.4.1999

I just happened to notice that the patchlevel number isn't updating on the website. I'm guessing an auto-update script has too low of an upper boundary assumption. - Christian -- "The term is 'Crackers', not 'Hackers,' by the way." "Whatever. What's the difference?" "Nothing I guess.

Re: [vim/vim] E36 from quickfix list (smaller than 3 lines) with noequalalways and buftype=nofile (#908)

On 9 July 2016, Christian Brabandt wrote: > On Fr, 08 Jul 2016, LCD 47 wrote: > > > Not recent, but do you remember the problem introduced by 1640? > > It's still with us. _shrug_ > > I don't follow. That was a bugfix for a crash and I believe it fixed > a crash that you

Re: Patch 7.4.1997

On 8 July 2016, LCD 47 wrote: > On 8 July 2016, Bram Moolenaar wrote: > > > > Lcd wrote: > > > > > On 7 July 2016, Bram Moolenaar wrote: > > > > > > > > Patch 7.4.1997 > > > > Problem:Cannot easily scroll the quickfix window. > >

Re: Patch to add the lbottom command

Yegappan wrote: > I am attaching a patch to implement the lbottom command (similar to > the newly added cbottom command). Thanks! -- hundred-and-one symptoms of being an internet addict: 243. You unsuccessfully try to download a pizza from www.dominos.com. /// Bram Moolenaar --

Re: Patch 7.4.2008

I wrote: > Patch 7.4.2008 > Problem:evalcmd() has a confusing name. > Solution: Rename to execute(). Make silent optional. Support a list of > commands. > Files: src/eval.c, src/ex_docmd.c, src/message.c, src/globals.h, > src/proto/eval.pro, src/Makefile,

Patch 7.4.2010

Patch 7.4.2010 Problem:There is a :cbottom command but no :lbottom command. Solution: Add :lbottom. (Yegappan Lakshmanan) Files: runtime/doc/index.txt, runtime/doc/quickfix.txt, src/ex_cmds.h, src/quickfix.c, src/testdir/test_quickfix.vim ***

Patch 7.4.2009

Patch 7.4.2009 (after 7.4.2008) Problem:Messages test fails. Solution: Don't set redir_execute before returning. Add missing version number. Files: src/eval.c *** ../vim-7.4.2008/src/eval.c 2016-07-09 17:05:49.203222428 +0200 --- src/eval.c 2016-07-09 17:32:54.263074518

Patch 7.4.2008

Patch 7.4.2008 Problem:evalcmd() has a confusing name. Solution: Rename to execute(). Make silent optional. Support a list of commands. Files: src/eval.c, src/ex_docmd.c, src/message.c, src/globals.h, src/proto/eval.pro, src/Makefile,

Re: Patch 7.4.1996

Nikolay Pavlov wrote: > >> I am also wondering why evalcmd()? When discussing the name in Neovim > >> bug tracker I was against `evalcmd()` because for `eval('expr')` > >> expression result is expected to be the only effect (though it is not > >> necessary, most expressions used with `eval()` do

Patch 7.4.2007

Patch 7.4.2007 Problem:Running the tests leaves a viminfo file behind. Solution: Make the viminfo option empty. Files: src/testdir/runtest.vim *** ../vim-7.4.2006/src/testdir/runtest.vim 2016-05-25 21:22:56.421828207 +0200 --- src/testdir/runtest.vim 2016-07-09

Patch 7.4.2006

Patch 7.4.2006 Problem:Crash when using tabnext in BufUnload autocmd. (Norio Takagi) Solution: First check that the current buffer is the right one. (Hirohito Higashi) Files: src/buffer.c, src/testdir/test_autocmd.vim *** ../vim-7.4.2005/src/buffer.c2016-07-03

Re: [vim/vim] E36 from quickfix list (smaller than 3 lines) with noequalalways and buftype=nofile (#908)

On Fr, 08 Jul 2016, LCD 47 wrote: > Not recent, but do you remember the problem introduced by 1640? > It's still with us. _shrug_ I don't follow. That was a bugfix for a crash and I believe it fixed a crash that you reported some time ago or so about accessing invalid memory when loading a

Re: Patch 7.4.1996

Hi Nikolay! On Sa, 09 Jul 2016, Nikolay Aleksandrovich Pavlov wrote: > 2016-07-08 13:36 GMT+03:00 Bram Moolenaar : > > > > Nikolay Pavlov wrote: > > > >> I am also wondering why evalcmd()? When discussing the name in Neovim > >> bug tracker I was against `evalcmd()` because

Re: [bugfix][patch] SEGV occurred when quit tabpage with autocmd BufUnload tabnext.

Hirohito Higashi wrote: > Hi Bram and Vimmers! > > How to reproduce: > $ cat sample.vim > tabedit > tabfirst > > augroup sample > autocmd! > autocmd BufUnload tabnext > augroup END > > quit > > > $ vim -Nu NONE -S sample.vim > > Expect bahavior: > - Keep 2 tabpages. > > Actual

Re: Some changes to the github notification mirror script

Hi Ingo! On Sa, 09 Jul 2016, Ingo Karkat wrote: > Hello Christian, > > speaking of the github notification mirror script, I noticed a possible bug. > > When I recently submitted an issue (https://github.com/vim/vim/issues/892), > the mirrored email got cut off just before a line that only

Re: Some changes to the github notification mirror script

Hello Christian, speaking of the github notification mirror script, I noticed a possible bug. When I recently submitted an issue (https://github.com/vim/vim/issues/892), the mirrored email got cut off just before a line that only contained a period (".", with whitespace indent in a Markdown