On Thursday, August 21, 2014 3:49:25 PM UTC+9, Lokesh Mandvekar wrote:
> Hi,
>
> I was hoping syntax highlighting for docker could be included by default in
> vim. The files can be found here:
> https://github.com/docker/docker/tree/master/contrib/syntax/vim
>
> Would the BSD license cause any tr
Ben, I do see your point now. And yes, it's probably best that distros use
upstream docker's vim files itself than having those sent over here which is an
added expense.
Bram, upto you to decide the fate of docker syntax files already included.
FWIW, fedora will have a docker-io-vim subpackage
Hi list.
vim.exe can't handle greek characters when encoding is utf-8. ex: β
In utf-8 encoding, β is 0xCE 0xB2. 0xCE is K_NUL. But it's not a tailing byte.
K_NUL must be escaped when it is contained in input bytes. But it don't need to
escape when it's a leading byte.
Below is a patch.
https://
On 13:07 Wed 17 Dec , Bram Moolenaar wrote:
>
> Marcin Szamotulski wrote:
>
> > On 20:11 Sat 13 Dec , Bram Moolenaar wrote:
> > >
> > > Marcin Szamotulski wrote:
> > >
> > > > I attach the promised patch for checking if the range is invalid.
> > >
> > > Thanks!
> >
> > Updated version
Ben Fritz wrote:
> On Wednesday, December 17, 2014 10:38:50 AM UTC-6, Bram Moolenaar wrote:
> >
> > This is one of those options that changes the behavior of Vim in a way
> > that many things work differently. I do want to discourage users from
> > setting it.
> >
> > Indeed, many plugins have
Updates:
Status: Fixed
Comment #3 on issue 296 by brammool...@gmail.com: Memory leak when using
viminfo and a vimrc
https://code.google.com/p/vim/issues/detail?id=296
Should be fixed by patch 7.4.560
--
You received this message because this project is configured to send all
issue
On Wednesday, December 17, 2014 10:38:50 AM UTC-6, Bram Moolenaar wrote:
>
> This is one of those options that changes the behavior of Vim in a way
> that many things work differently. I do want to discourage users from
> setting it.
>
> Indeed, many plugins have been fixed. That means they wer
Patch 7.4.560
Problem:Memory leak using :wviminfo. Issue 296.
Solution: Free memory when needed. (idea by Christian Brabandt)
Files: src/ops.c
*** ../vim-7.4.559/src/ops.c2014-12-17 18:35:37.553795955 +0100
--- src/ops.c 2014-12-17 20:59:49.722557613 +0100
***
*** 56
Patch 7.4.559
Problem:Appending a block in the middle of a tab does not work correctly
when virtualedit is set.
Solution: Decrement spaces and count, don't reset them. (James McCoy)
Files: src/ops.c, src/testdir/test39.in, src/testdir/test39.ok
*** ../vim-7.4.558/src/ops.c
Patch 7.4.558
Problem:When the X server restarts Vim may get stuck.
Solution: Destroy the application context and create it again. (Issue 203)
Files: src/os_unix.c
*** ../vim-7.4.557/src/os_unix.c2014-12-17 14:36:10.367090935 +0100
--- src/os_unix.c 2014-12-17 17:55:23.
Ben Fritz wrote:
> On Tuesday, December 16, 2014 9:49:48 AM UTC-6, Ingo Karkat wrote:
> >
> > On 16-Dec-2014 14:30, Axel Bender wrote:
> > > Using autochdir in .vimrc together with the --remote-silent start
> > > option works fine: the first edited file's path is set correctly.
> > > However, t
On Tuesday, December 16, 2014 9:49:48 AM UTC-6, Ingo Karkat wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 16-Dec-2014 14:30, Axel Bender wrote:
> > Using autochdir in .vimrc together with the --remote-silent start
> > option works fine: the first edited file's path is set correct
Patch 7.4.557
Problem:One more small issue.
Solution: Update function proto.
Files: src/proto/window.pro
*** ../vim-7.4.556/src/proto/window.pro 2014-06-17 17:48:21.780628008 +0200
--- src/proto/window.pro2014-11-12 15:34:22.895421553 +0100
***
*** 75,81
voi
Patch 7.4.556
Problem:Failed commands in Python interface not handled correctly.
Solution: Restore window and buffer on failure.
Files: src/if_py_both.h
*** ../vim-7.4.555/src/if_py_both.h 2014-08-29 13:49:48.678436915 +0200
--- src/if_py_both.h2014-09-19 14:21:33.474404353 +0
Patch 7.4.555
Problem:test_close_count may fail for some combination of features.
Solution: Require normal features.
Files: src/testdir/test_close_count.in
*** ../vim-7.4.554/src/testdir/test_close_count.in 2014-11-27
16:22:42.746412995 +0100
--- src/testdir/test_close_count.in
Patch 7.4.554
Problem:Missing part of patch 7.4.519.
Solution: Copy back regprog after calling vim_regexec.
Files: src/quickfix.c
*** ../vim-7.4.553/src/quickfix.c 2014-07-23 16:33:04.075886500 +0200
--- src/quickfix.c 2014-11-19 16:21:16.404128731 +0100
***
***
Patch 7.4.553
Problem:Various small issues.
Solution: Fix those issues.
Files: src/ex_cmds.h, src/gui.h, src/message.c, src/testdir/test39.in,
src/proto/eval.pro, src/proto/misc1.pro, src/proto/ops.pro,
src/proto/screen.pro, src/proto/window.pro. src/os_unix.c,
Yasuhiro Matsumoto wrote:
> On Tuesday, December 16, 2014 6:07:33 AM UTC+9, Bram Moolenaar wrote:
> > > This should work as updating register `"` with [].
> > >
> > > https://gist.github.com/mattn/1836e50933d4d186e7cd
> >
> > That's for any register, right?
>
> Yes, do you think it SHOULD NOT
Marcin Szamotulski wrote:
> On 20:11 Sat 13 Dec , Bram Moolenaar wrote:
> >
> > Marcin Szamotulski wrote:
> >
> > > I attach the promised patch for checking if the range is invalid.
> >
> > Thanks!
>
> Updated version, I figured out that 0 range is needed for :tabe.
Thanks. I tried inc
19 matches
Mail list logo
