Re: Patch for quickfix.txt

On 3/6/2017 2:02 PM, Bram Moolenaar wrote: Suresh Govindachar wrote: On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: [...] Thanks. Let's use backticks for commands and add a few commas: [...] Attached. --Suresh -- -- You received this message from the "vim_dev" maillist. Do

Re: [patch] neovim patches

2017-03-05 16:56 GMT+03:00 Bram Moolenaar : > > Justin M. Keyes wrote: > >> On Sat, Mar 4, 2017 at 10:10 PM, Christian Brabandt >> wrote: >> > On Sa, 04 Mär 2017, Bram Moolenaar wrote: >> > >> >> >> >> Christian Brabandt wrote: >> >> >> >> > On Di, 28 Feb

Re: [vim/vim] Ensure v:progpath is set to an absolute path (#1531)

Hi, 2017/3/7 Tue 9:12:21 UTC+9 James McCoy wrote: > On Mon, Mar 06, 2017 at 11:02:34PM +0100, Bram Moolenaar wrote: > > > > Michal Grochmal wrote: > > > > > I may be doing a horrible misinterpretation of the subject, but here goes > > > nothing. > > > > > > > > > > This just uses the existing

Re: [vim/vim] Ensure v:progpath is set to an absolute path (#1531)

On Mon, Mar 06, 2017 at 11:02:34PM +0100, Bram Moolenaar wrote: > > Michal Grochmal wrote: > > > I may be doing a horrible misinterpretation of the subject, but here goes > > nothing. > > > > > > > > This just uses the existing logic in mch_can_exe to populate a > > > > > > buffer with the > >

Re: [patch] neovim patches

Christian Brabandt wrote: > And another one that fixes the :move closes folds and :move invalidates > folds: > https://github.com/neovim/neovim/pull/6221 It's a bit big, but I suppose it's needed to make it work. Can someone turn this into a Vim patch? And check that it works, removing the

Re: Patch for quickfix.txt

Suresh Govindachar wrote: > On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: > > > > Attached patch to quickfix.txt is thanks to Tony Mechelynck. > > Updates to patch: minor wording changes; and now jumpable help tags are > enclosed in ||. Thanks. Let's use backticks for

Re: [vim/vim] Ensure v:progpath is set to an absolute path (#1531)

Michal Grochmal wrote: > I may be doing a horrible misinterpretation of the subject, but here goes > nothing. > > > > > > This just uses the existing logic in mch_can_exe to populate a buffer > > > > > with the > > > > > absolute path to the binary. The Windows code was already walking > > >

Re: Remaining references in indent plugins

Tyru wrote: > 2017-03-06 1:07 GMT+09:00 Bram Moolenaar : > > > > Tyru wrote: > > > >> > > I sent patches to indent plugins about shiftwidth(). > >> > > https://github.com/vim/vim/pull/578 > >> > > > >> > > And Bram has fixed it in these commits (thanks!). > >> > >

Re: Patch for quickfix.txt

Suresh Govindachar wrote: > Attached patch to quickfix.txt is thanks to Tony Mechelynck. Thanks. Let's add some highlighting and commas: A location list is a window-local quickfix list. You get one after commands like `:lvimgrep`, `:lgrep`, `:lhelpgrep`, `:lmake`, etc. which create a location

Re: Errors disabling folding

John Marriott wrote: > Disabling folding (FEAT_FOLDING) generates a number of compile errors, a > warning and a linking error (on HPUX and Windows), like so (this is on > Windows using mingw64): > ... > gcc -c -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 > -DHAVE_PATHDEF

Patch 8.0.0427

Patch 8.0.0427 Problem:'makeencoding' missing from the options window. Solution: Add the entry. Files: runtime/optwin.vim *** ../vim-8.0.0426/runtime/optwin.vim 2017-01-28 15:58:45.340197300 +0100 --- runtime/optwin.vim 2017-03-06 21:42:43.124400455 +0100 *** *** 1,7

Re: [vim/vim] Indent: bogus characters inserted in visual-block append

On Mo, 06 Mär 2017, Vitor Antunes wrote: > Well, at least the original issue would be fixed. When do you think > you will have your change merged? I am attaching an updated patch including some tests. Don't know when Bram comes to including this. Best, Christian -- Es gibt Personen, denen

Re: [vim/vim] Indent: bogus characters inserted in visual-block append

Hi Chistian, On Monday, 6 March 2017 20:18:33 UTC, Christian Brabandt wrote: > Hi Vitor! > > On Mo, 06 Mär 2017, Vitor Antunes wrote: > > Hope everything's alright with you. > > And since we're talking, any updates in this regard? ;P > > What you see is like removing characters when doing

Re: [vim/vim] Indent: bogus characters inserted in visual-block append

Hi Vitor! On Mo, 06 Mär 2017, Vitor Antunes wrote: > > The end result is much better now. But I did some extra testing and > > noticed > > that if the two lines start indented by 2* (which means the first line > > will be de-indented), then the second line will not have the ; appended. > > > >

Re: added TextDeleted and TextYanked events

Ben Fritz wrote: > On Saturday, March 4, 2017 at 6:47:33 AM UTC-6, Bram Moolenaar wrote: > > Philippe Vaucher wrote: > > > > > On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote: > > > > For the record, a version of this was merged into neovim: > > > >

Re: website: use SSL on windows binary download

Plato wrote: > Thanks for vim! > > As a privacy conscious user, I want some assurance that I am not installing > a binary that has been tampered with. > As a naive windows user, I don't have the knowledge or tools to verify > hashes. > > I found the HTTPS page at https://vim.sourceforge.io -

Patch 8.0.0426

Patch 8.0.0426 Problem:Insufficient testing for statusline. Solution: Add several tests. (Dominique Pelle, closes #1534) Files: src/testdir/test_statusline.vim *** ../vim-8.0.0425/src/testdir/test_statusline.vim 2016-04-04 23:03:08.0 +0200 ---

Re: [vim/vim] Indent: bogus characters inserted in visual-block append

Hi Christian, On Saturday, 25 February 2017 01:20:24 UTC, Vitor Antunes wrote: > On Friday, 24 February 2017 14:24:13 UTC, Christian Brabandt wrote: > > However here is a first play patch, that at least makes Vim aware that > > indenting could have taken place and tries to adjust to it. Please

Re: added TextDeleted and TextYanked events

> > ... > I don't personally feel the need for one, but I know many people would > like a "yank ring" style of plugin or other sort of clipboard management > which this patch would enable. > > FYI: YankRing.vim : Maintains a history of previous yanks, changes and deletes

Re: added TextDeleted and TextYanked events

On Saturday, March 4, 2017 at 6:47:33 AM UTC-6, Bram Moolenaar wrote: > Philippe Vaucher wrote: > > > On Monday, February 29, 2016 at 4:13:31 PM UTC+1, Björn Linse wrote: > > > For the record, a version of this was merged into neovim: > > > https://github.com/neovim/neovim/pull/4304 > > > >

Re: Patch for quickfix.txt

On 3/6/2017 6:17 AM, 'Suresh Govindachar' via vim_dev wrote: Attached patch to quickfix.txt is thanks to Tony Mechelynck. Updates to patch: minor wording changes; and now jumpable help tags are enclosed in ||. -- -- You received this message from the "vim_dev" maillist. Do not top-post!

mzscheme feature dist and version?

I'm trying to build a full-featured x64 Vim for Windows (via Cygwin) and lack only mzscheme. It fails against Racket 6.8, any tips on a better distribution or version? -- Steve Hall [ digitect dancingpaper com ] Cream for Vim http://cream.SourceForge.net -- -- You received this message from

Patch for quickfix.txt

Attached patch to quickfix.txt is thanks to Tony Mechelynck. --Suresh -- -- 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

Re: Remaining references in indent plugins

Hi Bram, 2017-03-06 1:07 GMT+09:00 Bram Moolenaar : > > Tyru wrote: > >> > > I sent patches to indent plugins about shiftwidth(). >> > > https://github.com/vim/vim/pull/578 >> > > >> > > And Bram has fixed it in these commits (thanks!). >> > >

Re: [patch] neovim patches

And another one that fixes the :move closes folds and :move invalidates folds: https://github.com/neovim/neovim/pull/6221 Best, Christian -- Wenn uns die Mächtigen ihre Zuneigung bekunden, dann ist Wahlzeit. -- Lothar Schmidt -- -- You received this message from the "vim_dev"

website: use SSL on windows binary download

Thanks for vim! As a privacy conscious user, I want some assurance that I am not installing a binary that has been tampered with. As a naive windows user, I don't have the knowledge or tools to verify hashes. I found the HTTPS page at https://vim.sourceforge.io - please follow through by

Errors disabling folding

Bram, Disabling folding (FEAT_FOLDING) generates a number of compile errors, a warning and a linking error (on HPUX and Windows), like so (this is on Windows using mingw64): ... gcc -c -Iproto -DWIN32 -DWINVER=0x0603 -D_WIN32_WINNT=0x0603 -DHAVE_PATHDEF -DFEAT_NORMAL -DHAVE_STDINT_H