Re: 'cindent' and 'cinkeys' with 0# inhibits of lines with # in column 1

2013-09-28 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: On Mi, 25 Sep 2013, Christian Brabandt wrote: On Mi, 25 Sep 2013, Christian Brabandt wrote: On Wed, September 25, 2013 15:21, Bram Moolenaar wrote: 'cinoptions' is for 'cindent' options. So do we agree, that cino=#N with N being non-zero would

[patch] Visual-block-change and cursor-keys

2013-09-28 Fir de Conversatie Christian Brabandt
Bram, when using Visual-block insert or append, you can't use the cursor keys to move the cursor to a different location. This will confuse vim. e.g. consider this block aaa bbb ccc Put the Cursor on the first a, and press lC-VjjlllIRightRightSpaceSpace The result will look like

[BUG] Two :silent! bugs: silencing exception disables :try/:catch and it does not work for :throw

2013-09-28 Fir de Conversatie ZyX
Try sourcing the following script function Fu() throw 1234 endfunction silent! call Fu() try|let b=au#xxx()|catch|echomsg v:exception|endtry . After you source it with “vim -u NONE -N -S script-name.vim” you will see Error detected while processing /tmp/zshubfJ7j:

Re: [patch] colorscheme autocommand should match against the colorscheme name

2013-09-28 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: currently, the colorscheme autocommand matches the pattern against the buffer name. I think, it would be more useful, to have the pattern match against the actual colorscheme name. So here is a patch, that changes it. I suppose the ColorScheme event is most

Re: [patch] colorscheme autocommand should match against the colorscheme name

2013-09-28 Fir de Conversatie ZyX
I suppose the ColorScheme event is most useful to make highlight changes after loading a color scheme. This depends on the color scheme, but may also depend on the syntax. This change is not backwards compatible, does that matter? I do not think so. I cannot imagine why somebody may want

[patch] shorten function name so it builds on VMS

2013-09-28 Fir de Conversatie Samuel Ferencik
Shorten the name of may_req_ambiguous_character_width to may_req_ambiguous_char_width so it builds on VMS. There's a limit of 31 characters, leading to truncation and consequently a failed build. Thanks, Sam === diff -r 3a32cbcc2449 src/main.c --- a/src/main.cWed Sep 25 23:24:58

Re: :spelldump not working

2013-09-28 Fir de Conversatie Dimitar DIMITROV
On Mo, 23 Sep 2013, Bram Moolenaar wrote: Christian Brabandt wrote: Hi Dimitar! On Mo, 23 Sep 2013, Dimitar DIMITROV wrote: Hi, Here is what I tried: :setlocal spelllang=bg spell then :spelldump and all I get is an empty window 'local' is the

Re: [patch] Visual-block-change and cursor-keys

2013-09-28 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: Bram, when using Visual-block insert or append, you can't use the cursor keys to move the cursor to a different location. This will confuse vim. e.g. consider this block aaa bbb ccc Put the Cursor on the first a, and press

Re: [BUG] Two :silent! bugs: silencing exception disables :try/:catch and it does not work for :throw

2013-09-28 Fir de Conversatie Bram Moolenaar
ZyX wrote: Try sourcing the following script function Fu() throw 1234 endfunction silent! call Fu() try|let b=au#xxx()|catch|echomsg v:exception|endtry . After you source it with “vim -u NONE -N -S script-name.vim” you will see Error detected while

Re: [BUG] Two :silent! bugs: silencing exception disables :try/:catch and it does not work for :throw

2013-09-28 Fir de Conversatie Nikolay Pavlov
On Sep 29, 2013 12:24 AM, Bram Moolenaar b...@moolenaar.net wrote: ZyX wrote: Try sourcing the following script function Fu() throw 1234 endfunction silent! call Fu() try|let b=au#xxx()|catch|echomsg v:exception|endtry . After you source it with “vim -u

[patch] on VMS, prevent freeze when Esc is pressed on E325

2013-09-28 Fir de Conversatie Samuel Ferencik
On the E325 screen (Found a swap file...), the user can choose different keys to press (e.g. [O]pen Read-Only, (E)dit anyway,...). If she presses Esc, vim freezes (and the terminal session has to be killed). Reproduce as follows: 1) in one terminal, $ vim a.txt 2) in another terminal, $ vim a.txt