Re: make v:shell_error writable

On Tue, Sep 27, 2016 at 10:10 PM, Christian Brabandt wrote: > Bram, > I maintain the popular eye-candy plugin vim-airline. For files > maintained in git, it checks the current branch and displays it in the > statusline using system('git status...') and caches the result, so

Re: update to todo.txt

Hi, 2016/9/28 Wed 4:58:00 UTC+9 Bram Moolenaar wrote: > Christian Brabandt wrote: > > > I attach an update to todo.txt > > > > I cleaned it up a little, removed some duplicates and removed some > > things, that have been solved differently in the meantime. However some > > of those changes

Re: make v:shell_error writable

Christian Brabandt wrote: > Bram, > I maintain the popular eye-candy plugin vim-airline. For files > maintained in git, it checks the current branch and displays it in the > statusline using system('git status...') and caches the result, so that > it is not called to often. However after a

make v:shell_error writable

Bram, I maintain the popular eye-candy plugin vim-airline. For files maintained in git, it checks the current branch and displays it in the statusline using system('git status...') and caches the result, so that it is not called to often. However after a ShellCmdPost autocommand, it

Re: Patch 8.0.0014

Kazunobu Kuriyama wrote: > 2016-09-27 3:15 GMT+09:00 Bram Moolenaar : > > > > > Patch 8.0.0014 > > Problem:Crypt tests are old style. > > Solution: Convert to new style. > > Files: src/testdir/test71.in, src/testdir/test71.ok, > >

Re: update to todo.txt

Christian Brabandt wrote: > I attach an update to todo.txt > > I cleaned it up a little, removed some duplicates and removed some > things, that have been solved differently in the meantime. However some > of those changes could be controversial, so you might not want to take > over each

Re: Patch 7.4.2200

On 27 September 2016, Yegappan Lakshmanan wrote: > Hi, > > On Fri, Sep 16, 2016 at 11:32 PM, LCD 47 wrote: > > On 16 September 2016, Yegappan Lakshmanan wrote: > >> Hi, > >> > >> On Sun, Sep 11, 2016 at 4:08 AM, LCD 47

Re: Patch 7.4.2200

Yegappan Lakshmanan wrote: > On Fri, Sep 16, 2016 at 11:32 PM, LCD 47 wrote: > > On 16 September 2016, Yegappan Lakshmanan wrote: > >> Hi, > >> > >> On Sun, Sep 11, 2016 at 4:08 AM, LCD 47 wrote: > >> > On 12 August 2016, Bram Moolenaar

Patch 8.0.0017

Patch 8.0.0017 Problem:Cannot get the number of the current quickfix or location list. Solution: Use the current list if "nr" in "what" is zero. (Yegappan Lakshmanan) Remove debug command from test. Files: src/quickfix.c, src/testdir/test_quickfix.vim,

update to todo.txt

Bram, I attach an update to todo.txt I cleaned it up a little, removed some duplicates and removed some things, that have been solved differently in the meantime. However some of those changes could be controversial, so you might not want to take over each change. Also, I have annotated one

Re: setpos() behaves erratically at times

@ Christian Thanks for your reply. I know that the mode cannot be possibly guessed from the positions used with setpos() (although some rough guesses could be made). That's why I proposed to have an extra parameter to setpos() or visualmode() (instead of calling e.g. execute "normal v\") some

Re: setpos() behaves erratically at times

Hi Axel! On Di, 27 Sep 2016, Axel Bender wrote: > There's no direct connection. It was however the origin of my > "troubles". The main problem - meanwhile - is the behavior of > setpos()/getpos(). When setting "'<" and "'>" vim takes into > consideration the last Visual mode, which is not what I

Re: setpos() behaves erratically at times

There's no direct connection. It was however the origin of my "troubles". The main problem - meanwhile - is the behavior of setpos()/getpos(). When setting "'<" and "'>" vim takes into consideration the last Visual mode, which is not what I would have expected (and haven't found any

Re: Patch 7.4.2200

Hi, On Fri, Sep 16, 2016 at 11:32 PM, LCD 47 wrote: > On 16 September 2016, Yegappan Lakshmanan wrote: >> Hi, >> >> On Sun, Sep 11, 2016 at 4:08 AM, LCD 47 wrote: >> > On 12 August 2016, Bram Moolenaar wrote: >> >>

Re: setpos() behaves erratically at times

Hi Axel! On Di, 27 Sep 2016, Axel Bender wrote: > Thanks for your reply. > > From my point of view this a joint problem of getpos()/setpos() - > unless the docs state it's not (I haven't found any info on that > though; I found something (inofficial) here however: >

Re: setpos() behaves erratically at times

Thanks for your reply. >From my point of view this a joint problem of getpos()/setpos() - unless the >docs state it's not (I haven't found any info on that though; I found >something (inofficial) here however: >http://learnvimscriptthehardway.stevelosh.com/chapters/15.html). Maybe there

Re: Patch 8.0.0014

2016-09-27 3:15 GMT+09:00 Bram Moolenaar : > > Patch 8.0.0014 > Problem:Crypt tests are old style. > Solution: Convert to new style. > Files: src/testdir/test71.in, src/testdir/test71.ok, > src/testdir/test71a.in, src/testdir/test_crypt.vim, >

Re: setpos() behaves erratically at times

Hi, Axel Bender schrieb am 25.09.2016 um 12:36: > IS the conclusion I made in my previous post correct? > > Can we generally NOT assume to start in CHARWISE Visual mode when entering > operator-pending mode? > > If so, where would that be described in the docs? I'm not sure, but you are