docker syntax files

2014-08-20 Fir de Conversatie Lokesh Mandvekar
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 trouble in this matter? Thanks, -- Lokesh pgpeuXBUWT3pd.pgp Description: PGP signat

Re: [Bulk] Re: Add count to :close and :hide commands

2014-08-20 Fir de Conversatie Christian Brabandt
Am 2014-08-20 19:03, schrieb 'Andy Wokula' via vim_dev: Some people expect :1,$bd or :%bd to delete all buffers. That only works by accident, because your current buffer has more lines than you have open buffers. Or saying it differently, this does not work in an empty buffer. So this expe

Re: [Bulk] Re: [patch] :undorecover command

2014-08-20 Fir de Conversatie Christian Brabandt
Am 2014-08-20 19:03, schrieb 'Andy Wokula' via vim_dev: Am 16.08.2014 21:25, schrieb Christian Brabandt: The command is named ":undorecover"? Some places use ":undorecovery" (help, EMSG). The command is called :undorecover, but the process of doing so is undorecovery, isn't it? Best, Christia

Re: {func} of sort()

2014-08-20 Fir de Conversatie mattn
About making list sorted by string of one of value. echo "3" < "3 0" This is TRUE, then: echo MapSort([{"foo":{"bar": "3"}}, {"foo":{"bar": "3 0"}}], 'v:val["foo"]["bar"]') We expecet it should be kept: [{"foo":{"bar": "3"}}, {"foo":{"bar": "3 0"}}] But results are: [{'foo': {'bar': '3 0'}}

Re: [patch] improper indentation with shell case statements (ft=sh)

2014-08-20 Fir de Conversatie Gary Johnson
As long as you're working on indent/sh.vim, would you please look at fixing this, too? { echo this } ( echo that ) The problem is that statements within parentheses are not indented. They should be indented the same as statements within braces. Regards, Gary -- --

Re: Issue 250 in vim: Random US-International keyboard layout (dead keys) support

2014-08-20 Fir de Conversatie vim
Comment #7 on issue 250 by john.wel...@gmail.com: Random US-International keyboard layout (dead keys) support http://code.google.com/p/vim/issues/detail?id=250 I came up with a much nicer solution that actually addresses the underlying issue and that decreases Vim's size^^ Besides this bu

Re: [BUG] Groovy regexp syntax highlighting in Vim 7.4

2014-08-20 Fir de Conversatie google
On Tuesday, September 17, 2013 2:05:48 PM UTC-4, rdolgushin wrote: > For details see > http://stackoverflow.com/questions/18855809/groovy-syntax-highlighting-in-vim-7-4 > > Possible sollution: delete or comment this line > https://code.google.com/p/vim/source/browse/runtime/syntax/groovy.vim?r=

Re: [Bulk] Re: [patch] :undorecover command

2014-08-20 Fir de Conversatie 'Andy Wokula' via vim_dev
Am 16.08.2014 21:25, schrieb Christian Brabandt: The command is named ":undorecover"? Some places use ":undorecovery" (help, EMSG). -- Andy -- -- 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, vis

Re: [Bulk] Re: Add count to :close and :hide commands

2014-08-20 Fir de Conversatie 'Andy Wokula' via vim_dev
Am 10.08.2014 20:33, schrieb Marcin Szamotulski: On 15:51 Sun 10 Aug , Bram Moolenaar wrote: I wrote: Marcin Szamotulski wrote: I wrote a patch which adds [count] to :colse, :hide and ^Wc normal command. When given the window with window number [count] will be closed/hidden. Sometimes

Re: {func} of sort()

2014-08-20 Fir de Conversatie 'Andy Wokula' via vim_dev
Am 19.08.2014 um 11:17 schrieb mattn: Keys? v:key is list index, it cannot contain spaces. Spaces in values shouldn't matter. Not sure what you mean. I wonder this won't works correctly. [{"a": "b"}, {"a b": ""}] Guessing you want to sort by dict key: :echo MapSort([{"a": "b"}, {"a b":

Re: breakindent bug

2014-08-20 Fir de Conversatie Bram Moolenaar
Christian wrote: > On Di, 19 Aug 2014, Bram Moolenaar wrote: > > > Thanks. Somehow for me appending _bug means you test for the bug to be > > present :-). We can just call it test_linebreak. Oh, and keep them in > > alphabetical order. I started doing that recently. > > Okay, how about that

Re: Issue 250 in vim: Random US-International keyboard layout (dead keys) support

2014-08-20 Fir de Conversatie vim
Comment #6 on issue 250 by christ.v...@coosto.com: Random US-International keyboard layout (dead keys) support http://code.google.com/p/vim/issues/detail?id=250 Looks like a solution. Increases Vim's size by SIZEOF(MSG) again, though :-) -- You received this message because this project is c

Re: Issue 250 in vim: Random US-International keyboard layout (dead keys) support

2014-08-20 Fir de Conversatie vim
Comment #5 on issue 250 by john.wel...@gmail.com: Random US-International keyboard layout (dead keys) support http://code.google.com/p/vim/issues/detail?id=250 I've found and fixed the problem. Here is a patch. A custom MSG structure used for sending a fake VK_SPACE was declared locally be

Re: Issue 250 in vim: Random US-International keyboard layout (dead keys) support

2014-08-20 Fir de Conversatie vim
Comment #4 on issue 250 by chrisbr...@googlemail.com: Random US-International keyboard layout (dead keys) support http://code.google.com/p/vim/issues/detail?id=250 Can you try, if building without optimiziations fixes your issue as well? -- You received this message because this project is c

Re: breakindent bug

2014-08-20 Fir de Conversatie Christian Brabandt
On Di, 19 Aug 2014, Bram Moolenaar wrote: > Thanks. Somehow for me appending _bug means you test for the bug to be > present :-). We can just call it test_linebreak. Oh, and keep them in > alphabetical order. I started doing that recently. Okay, how about that one (I added a small README.txt