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
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
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
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
Hi Bram,
On Mon, Apr 29, 2019 at 11:31 AM Bram Moolenaar wrote:
>
> Yegappan wrote:
>
> > On Mon, Apr 29, 2019 at 7:54 AM Yegappan Lakshmanan
> > wrote:
> > >
> > > Hi,
> > >
> > > On Mon, Apr 29, 2019 at 7:48 AM Andy Massimino
> > > wrote:
> > > >
> > > > So does :cabo 3 mean move to the thir
On Mon, Apr 29, 2019 at 8:31 PM Bram Moolenaar wrote:
>
>
> Tony wrote:
>
> > 1. hg --verbose clone https://bitbucket.org/vim-mirror/vim vim-hg
> > 2. cd vim-hg/src
> > 3. make distclean # IMPORTANT! otherwise "make shadow" will run
> > configure first)
> > 4. SHADOWDIR=shadow-huge make -e shado
Patch 8.1.1239
Problem:Key with byte sequence containing CSI does not work.
Solution: Do not recognize CSI as special unless the GUI is active. (Ken
Takata, closes #4318)
Files: src/getchar.c
*** ../vim-8.1.1238/src/getchar.c 2019-04-28 19:46:17.026060122 +0200
---
Patch 8.1.1238
Problem:MS-Windows: compiler warning for sprintf() format.
Solution: Change %d to %ld. (Ken Takata)
Files: src/gui_w32.c
*** ../vim-8.1.1237/src/gui_w32.c 2019-04-28 19:46:17.026060122 +0200
--- src/gui_w32.c 2019-04-29 21:45:29.693539165 +0200
Ken Takata wrote:
> After the patch 8.1.1224, MinGW warns this:
>
> gui_w32.c: In function 'logfont2name':
> gui_w32.c:3132:35: warning: format '%d' expects argument of type 'int', but
> argument 5 has type 'LONG {aka long int}' [-Wformat=]
> sprintf((char *)p, "%s:h%d:W%d", font_name, p
Le lundi 29 avril 2019 21:31:08 UTC+2, Bram Moolenaar a écrit :
> Ken Takata wrote:
>
> > 2019/4/29 Mon 0:02:09 UTC+9 niva...@gmail.com wrote:
> > > Hi All,
> > >
> > > Since v8.1.1210, I encounter this error :
> > >
> > > -o gobji686/if_ole.o if_ole.cpp
> > > In file included from proto.h:230:0
Ken Takata wrote:
> 2019/4/29 Mon 0:02:09 UTC+9 niva...@gmail.com wrote:
> > Hi All,
> >
> > Since v8.1.1210, I encounter this error :
> >
> > -o gobji686/if_ole.o if_ole.cpp
> > In file included from proto.h:230:0,
> > from vim.h:2084,
> > from if_ole.cpp:22:
Patch 8.1.1237
Problem:Error for using "compl", reserved word in C++.
Solution: Rename to "complp". (suggestion by Ken Takata)
Files: src/usercmd.c, src/proto/usercmd.pro
*** ../vim-8.1.1236/src/usercmd.c 2019-04-27 13:03:20.000715982 +0200
--- src/usercmd.c 2019-04-29 21
Hi and thanks a lot Ken.
I thought that msys2 and make ming, was less heavy than msvc.
I prefer using compiler more strict.
It seems that no much People is using msys2 and ming to build vim regarding up
to 20 patchs to get some reply.
Thank you Ken
NiVa
--
--
You received this message from
Hi and thanks a lot Ken.
I thought that msys2 and make ming, was less heavy than msvc.
I prefer using compiler more strict.
It seems that no much People is using msys2 and ming to build vim regarding
up to 20 patchs to get some reply.
Thank you Ken
NiVa
Le lun. 29 avr. 2019 à 20:20, a écrit :
Tony wrote:
> 1. hg --verbose clone https://bitbucket.org/vim-mirror/vim vim-hg
> 2. cd vim-hg/src
> 3. make distclean # IMPORTANT! otherwise "make shadow" will run
> configure first)
> 4. SHADOWDIR=shadow-huge make -e shadow
> 5. cd shadow-huge
> 6. ln -svf ../Makefile
> 7. ln -sv ../../../hu
Tony wrote:
> P.S. I tried popping the changes into an mq patch. Strangely enough,
> AFAICT the changes done by "make" in the desktop files seem to consist
> in the _removal_ of the German localizations (see attachment).
Those lines should be duplicates, was fixed in 8.1.1227.
--
Trees moving
Hi,
After the patch 8.1.1224, MinGW warns this:
gui_w32.c: In function 'logfont2name':
gui_w32.c:3132:35: warning: format '%d' expects argument of type 'int', but
argument 5 has type 'LONG {aka long int}' [-Wformat=]
sprintf((char *)p, "%s:h%d:W%d", font_name, points, lf.lfWeight);
Yegappan wrote:
> On Mon, Apr 29, 2019 at 7:54 AM Yegappan Lakshmanan
> wrote:
> >
> > Hi,
> >
> > On Mon, Apr 29, 2019 at 7:48 AM Andy Massimino
> > wrote:
> > >
> > > So does :cabo 3 mean move to the third error, counting up, above the
> > > current line?
> > >
> >
> > Yes. If the specifie
Patch 8.1.1236
Problem:sjiscorr.c not found in shadow directory. (Tony Mechelynck)
Solution: Link po/*.c files with "make shadow".
Files: src/Makefile
*** ../vim-8.1.1235/src/Makefile2019-04-27 18:00:29.851064563 +0200
--- src/Makefile2019-04-29 20:27:43.896129717 +02
Hi,
2019/4/29 Mon 0:02:09 UTC+9 niva...@gmail.com wrote:
> Hi All,
>
> Since v8.1.1210, I encounter this error :
>
> -o gobji686/if_ole.o if_ole.cpp
> In file included from proto.h:230:0,
> from vim.h:2084,
> from if_ole.cpp:22:
> proto/usercmd.pro:2:74: error:
Patch 8.1.1235
Problem:Compiler warnings for using STRLEN() value.
Solution: Cast to int. (Christian Brabandt, Mike Williams)
Files: src/tag.c
*** ../vim-8.1.1234/src/tag.c 2019-04-28 18:04:56.062492159 +0200
--- src/tag.c 2019-04-29 19:43:43.182061855 +0200
***
*** 1
Christian wrote:
> On So, 28 Apr 2019, Bram Moolenaar wrote:
>
> > Patch 8.1.1228
> > Problem:Not possible to process tags with a function.
> > Solution: Add tagfunc() (Christian Brabandt, Andy Massimino, closes #4010)
>
> I see some warnings on appveyor after this patch. Can you please
Hello Vim developers,
the JSON filetype is pretty common, so I'd like to mention that the current
author of the JSON syntax script (https://github.com/elzr) doesn't seem to
maintain the plugin any longer, and maybe someone else wants to adopt the
syntax plugin.
Eli's last GitHub contribution w
Hi,
On Mon, Apr 29, 2019 at 8:09 AM Christian Brabandt
wrote:
>
> Each entry in the current line is treated as separate entries. If the current
> line has 3 entries and the specified count is 2, then the cursor will not be
> moved.
>
> So with a window like this (cursor is [|], error marked as
Hi,
On Mon, Apr 29, 2019 at 7:54 AM Yegappan Lakshmanan wrote:
>
> Hi,
>
> On Mon, Apr 29, 2019 at 7:48 AM Andy Massimino
> wrote:
> >
> > So does :cabo 3 mean move to the third error, counting up, above the
> > current line?
> >
>
> Yes. If the specified count exceeds the number of entries abo
Hi,
On Mon, Apr 29, 2019 at 7:48 AM Andy Massimino
wrote:
>
> So does :cabo 3 mean move to the third error, counting up, above the current
> line?
>
Yes. If the specified count exceeds the number of entries above the
current line,
then it stops at the first error in the file.
>
> What if there
Hi Bram,
On Sat, Apr 27, 2019 at 10:11 AM Bram Moolenaar wrote:
>
> Yegappan wrote:
>
> > I came across the following threads that discuss about the need
> > for a command to jump to the next quickfix entry relative to the
> > current file:
> >
> > https://vi.stackexchange.com/questions/14356/go-
On So, 28 Apr 2019, Bram Moolenaar wrote:
> Patch 8.1.1228
> Problem:Not possible to process tags with a function.
> Solution: Add tagfunc() (Christian Brabandt, Andy Massimino, closes #4010)
I see some warnings on appveyor after this patch. Can you please include
the following patch:
d
28 matches
Mail list logo