Re: E484 after GVIM update

2019-05-22 Fir de Conversatie Ken Takata
Hi, 2019/5/23 Thu 9:36:27 UTC+9 Ken Takata wrote: > That's too bad. > Unfortunately, I cannot repoduce this yet. > Does this simple case work? > > gvim --clean > :echo system('dir') > > Does the problem occur only with gvim? not on vim.exe? Ah! `gui.in_use` is not set when system() is execu

Re: E484 after GVIM update

2019-05-22 Fir de Conversatie Ken Takata
Hi, 2019/5/23 Thu 5:29:48 UTC+9 Bram Moolenaar wrote: > > > 2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote: > > > > Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit : > > > > > Hi, > > > > > > > > > > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote: > > > > > > Le vendredi 3 mai 2019 00:36:56 UTC+2,

Re: Listener functionality

2019-05-22 Fir de Conversatie Bram Moolenaar
Paul Jolly wrote: > > Up to you. You can merge the changes into one, keeping the lowest > > changed line number and the total deleted/added lines, or you can deal > > with each change separately. > > I'm not sure I see how the change can be handled separately (without > carrying forward positi

Re: [bug] Session file does not restore correct current window on each tab page

2019-05-22 Fir de Conversatie Jason Franklin
> Wel already do use :argadd actually, when starting with "vim file1 > file2". The first buffer is wiped out, we just don't have buffer number > one. I think this is not true if 'hidden' is set. I failed to include that in my example though. Sorry for being unclear there. With 'hidden' the bu

Patch 8.1.1365

2019-05-22 Fir de Conversatie Bram Moolenaar
Patch 8.1.1365 Problem:Source command doesn't check for the sandbox. (Armin Razmjou) Solution: Check for the sandbox when sourcing a file. Files: src/getchar.c, src/testdir/test_source.vim *** ../vim-8.1.1364/src/getchar.c 2019-05-19 21:57:05.670320399 +0200 --- src/getchar.c

Re: Listener functionality

2019-05-22 Fir de Conversatie Bram Moolenaar
Paul Jolly wrote: > Thanks for your other response. Not sure whether my message below came > through. > > It seems I'm going to have to do a bit more work on the list of > changes that comes through. > > In the example, I think I actually need to collapse the two changes > into a single one w

Re: [bug] Session file does not restore correct current window on each tab page

2019-05-22 Fir de Conversatie Bram Moolenaar
Jason Franklin wrote: > > Perhaps using :argadd works to create the buffers without actually > > opening them or any other side effects. Then later reset the > > argument list. > > I think it's even trickier than using :argadd. For example... > > vim --clean > :argadd test.txt > :e tes

Re: E484 after GVIM update

2019-05-22 Fir de Conversatie Bram Moolenaar
> > 2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote: > > > Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit : > > > > Hi, > > > > > > > > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote: > > > > > Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a écrit : > > > > > > On Tuesday, April 30, 2019 at 11:3

Re: Listener functionality

2019-05-22 Fir de Conversatie Paul Jolly
Thanks very much. > Up to you. You can merge the changes into one, keeping the lowest > changed line number and the total deleted/added lines, or you can deal > with each change separately. I'm not sure I see how the change can be handled separately (without carrying forward position changes) in

Re: [bug] Session file does not restore correct current window on each tab page

2019-05-22 Fir de Conversatie Jason Franklin
Bram, > Perhaps using :argadd works to create the buffers without actually > opening them or any other side effects. Then later reset the > argument list. I think it's even trickier than using :argadd. For example... vim --clean :argadd test.txt :e test.txt Notice that you're now editin

Re: Listener functionality

2019-05-22 Fir de Conversatie Bram Moolenaar
Paul Jolly wrote: > Thanks for your patience with this! > > > So the first list are the lines in the buffer? > > Yes, correct. > > > > ['const x = ``'] [{'lnum': 1, 'col': 11, 'added': 0, 'end': 2}, {'lnum': > > > 1, 'col': 12, 'added': 0, 'end': 2}] > > > > Here you type the first backtick,

Re: Listener functionality

2019-05-22 Fir de Conversatie Paul Jolly
Thanks for your other response. Not sure whether my message below came through. It seems I'm going to have to do a bit more work on the list of changes that comes through. In the example, I think I actually need to collapse the two changes into a single one with added = 2. Then do a pass over th

Re: Listener functionality

2019-05-22 Fir de Conversatie Bram Moolenaar
Paul Jolly wrote: > > Here you type Enter twice. > > Not sure if it's significant, but I only hit enter once. The plugin makes > the second change here. It matters in the sense that there is no screen redraw in between. If you would have typed really fast then the same thing would have happene

Re: Listener functionality

2019-05-22 Fir de Conversatie Paul Jolly
> > Here you type Enter twice. Not sure if it's significant, but I only hit enter once. The plugin makes the second change here. -- -- 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://

Re: Listener functionality

2019-05-22 Fir de Conversatie Paul Jolly
Thanks for your patience with this! > So the first list are the lines in the buffer? Yes, correct. > > ['const x = ``'] [{'lnum': 1, 'col': 11, 'added': 0, 'end': 2}, {'lnum': 1, > > 'col': 12, 'added': 0, 'end': 2}] > > Here you type the first backtick, and the plugin adds the second > backtic

Re: E484 after GVIM update

2019-05-22 Fir de Conversatie Ni Va
Le jeudi 16 mai 2019 09:04:54 UTC+2, Ken Takata a écrit : > Hi, > > 2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote: > > Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit : > > > Hi, > > > > > > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote: > > > > Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a é

Re: Listener functionality

2019-05-22 Fir de Conversatie Bram Moolenaar
Paul Jolly wrote: > > Good luck. Let me know when something doesn't work properly, we can > > still adjust the functionality for a week or so. Well, once you use it > > we should probably not change it anymore. > > Hi Bram, > > Good news: I have delta based updates from govim -> gopls largel

Re: Listener functionality

2019-05-22 Fir de Conversatie Paul Jolly
> Good luck. Let me know when something doesn't work properly, we can > still adjust the functionality for a week or so. Well, once you use it > we should probably not change it anymore. Hi Bram, Good news: I have delta based updates from govim -> gopls largely working. But there appears to be