Re: E484 after GVIM update

2019-05-23 Fir de Conversatie Bram Moolenaar
Ken Takata wrote: > 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_

Re: E484 after GVIM update

2019-05-23 Fir de Conversatie Ni Va
Le jeudi 23 mai 2019 08:03:20 UTC+2, Ken Takata a écrit : > 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 onl

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: 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: 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: E484 after GVIM update

2019-05-16 Fir de Conversatie Ken Takata
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 écrit : > > > > On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wr

Re: E484 after GVIM update

2019-05-15 Fir de Conversatie Ni Va
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:36:39 AM UTC-4, Blay263 wrote: > > > > On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4

Re: E484 after GVIM update

2019-05-15 Fir de Conversatie Ken Takata
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:36:39 AM UTC-4, Blay263 wrote: > > > On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote: > > > > Le mardi 30 avril 2019 08:49:27 UTC+2,

Re: E484 after GVIM update

2019-05-15 Fir de Conversatie Ni Va
Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a écrit : > On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wrote: > > On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote: > > > Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > > > > Le mardi 30 avril

Re: E484 after GVIM update

2019-05-02 Fir de Conversatie Blay263
On Tuesday, April 30, 2019 at 11:36:39 AM UTC-4, Blay263 wrote: > On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote: > > Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > > > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit : > > > > On Mo,

Re: E484 after GVIM update

2019-04-30 Fir de Conversatie Blay263
On Tuesday, April 30, 2019 at 3:31:31 AM UTC-4, niva...@gmail.com wrote: > Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit : > > > On Mo, 29 Apr 2019, Blay263 wrote: > > > > > > > After updating my vim version

Re: E484 after GVIM update

2019-04-30 Fir de Conversatie nivaemail
Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit : > > On Mo, 29 Apr 2019, Blay263 wrote: > > > > > After updating my vim version I am getting the error below: > > > > > > E484: Can't open file C:\Users\\Ap

Re: E484 after GVIM update

2019-04-29 Fir de Conversatie nivaemail
Le mardi 30 avril 2019 08:49:27 UTC+2, niva...@gmail.com a écrit : > Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit : > > On Mo, 29 Apr 2019, Blay263 wrote: > > > > > After updating my vim version I am getting the error below: > > > > > > E484: Can't open file C:\Users\\Ap

Re: E484 after GVIM update

2019-04-29 Fir de Conversatie nivaemail
Le mardi 30 avril 2019 07:46:42 UTC+2, Christian Brabandt a écrit : > On Mo, 29 Apr 2019, Blay263 wrote: > > > After updating my vim version I am getting the error below: > > > > E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp > > > > I am using GVIM on windows with the WSL s

Re: E484 after GVIM update

2019-04-29 Fir de Conversatie Christian Brabandt
On Mo, 29 Apr 2019, Blay263 wrote: > After updating my vim version I am getting the error below: > > E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp > > I am using GVIM on windows with the WSL subsytem. It looks like the way the > escape sequences work has changed. So wha

E484 after GVIM update

2019-04-29 Fir de Conversatie Blay263
After updating my vim version I am getting the error below: E484: Can't open file C:\Users\\AppData\Local\Temp\VIoCC2F.tmp I am using GVIM on windows with the WSL subsytem. It looks like the way the escape sequences work has changed. -- -- You received this message from the "vim_dev" mai