Bug? Incorrect c-indent with braces inside parentheses

2011-09-07 Fir de Conversatie Sektor van Skijlen
Hello, With this set of cinoptions: cinoptions=:0,=1s,g0,j1 Vim has formatted the following text automatically this way: a( { b { } } ); It makes a difference, when you place a

Re: Bug? Incorrect c-indent with braces inside parentheses

2011-09-07 Fir de Conversatie Lech Lorens
On 7 September 2011 09:26, Sektor van Skijlen ethou...@gmail.com wrote: Hello, With this set of cinoptions: cinoptions=:0,=1s,g0,j1 [...] I can't find anything about this - is that already fixed? I don't think so (doesn't work for me on Vim 7.3.189 unless I remove the j1 setting from

Re: Bug? Incorrect c-indent with braces inside parentheses

2011-09-07 Fir de Conversatie Dominique Pellé
Lech Lorens lech.lor...@gmail.com wrote: On 7 September 2011 09:26, Sektor van Skijlen ethou...@gmail.com wrote: Hello, With this set of cinoptions: cinoptions=:0,=1s,g0,j1 [...] I can't find anything about this - is that already fixed? I don't think so (doesn't work for me on Vim

Re: Patch 7.3.294

2011-09-07 Fir de Conversatie Bram Moolenaar
Taro Muraoka wrote: Perhaps the complete function should somehow indicate that it must be called whenever the leader changes. I thought about that too. It would be better that second 'complefunc' option, like 'completefunc2'. Of course 'completefunc2' prior to 'completefunc' when

Re: Incorrect preprocessor highlighting in cpp filetype

2011-09-07 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: Hi François! On Mo, 05 Sep 2011, François Ingelrest wrote: Hi all, The following code is highlighted incorrectly when using the cpp filetype: #if defined FOO #elif defined BAR #endif The part defined BAR is not highlighted, while defined FOO

Re: Crash on autocomplete - code dereferences null pointer (with patch)

2011-09-07 Fir de Conversatie Bram Moolenaar
Gasper Azman wrote: (Note: I can't post to this list yet, a mod has to approve this email. I'm also sorry for the gmail chat invites gmail spammed in my name, an unlucky misclick caused that and I didn't know how to stop it. I also sent this patch yesterday already, but it seems every one of

Re: Patch 7.3.294

2011-09-07 Fir de Conversatie MURAOKA Taro
Hmm. It seems too tricky. How about this more formed idea. Vim can check type of returned value from completefunc, so vim should accept not only array but also dictionary. For array value, vim use it as same as currently. For dictionary value, vim behaves some parsing on it. For example,

Patch 7.3.296

2011-09-07 Fir de Conversatie Bram Moolenaar
Patch 7.3.296 Problem:When writing to an external command a zombie process may be left behind. Solution: Wait on the process. (James Vega) Files: src/os_unix.c *** ../vim-7.3.295/src/os_unix.c2011-09-07 14:06:38.0 +0200 --- src/os_unix.c 2011-09-07

Fwd: unexpected behavior of :let-@

2011-09-07 Fir de Conversatie Benjamin Fritz
I posted this a while ago on vim_use, but no response. It looks like either a bug or a very misleading :help entry. The thread is about how using :let-@ will automatically append a ^J character if the text ends in ^M (useful for yanked text, but causes unintended side effects when editing a

Re: Patch 7.3.294

2011-09-07 Fir de Conversatie Bram Moolenaar
Taro Muraoka wrote: Hmm. It seems too tricky. How about this more formed idea. Vim can check type of returned value from completefunc, so vim should accept not only array but also dictionary. For array value, vim use it as same as currently. For dictionary value, vim behaves some

Re: Crash on autocomplete - code dereferences null pointer (with patch)

2011-09-07 Fir de Conversatie Gašper Ažman
On Wed, Sep 7, 2011 at 13:56, Bram Moolenaar b...@moolenaar.net wrote: Gasper Azman wrote: (Note: I can't post to this list yet, a mod has to approve this email. I'm also sorry for the gmail chat invites gmail spammed in my name, an unlucky misclick caused that and I didn't know how to stop

Patch 7.3.298

2011-09-07 Fir de Conversatie Bram Moolenaar
Patch 7.3.298 Problem:Built-in colors are different from rgb.txt. Solution: Adjust the color values. (Benjamin Haskell) Files: src/gui_photon.c, src/gui_w48.c *** ../vim-7.3.297/src/gui_photon.c 2011-08-10 12:19:00.0 +0200 --- src/gui_photon.c2011-09-07

Patch 7.3.299

2011-09-07 Fir de Conversatie Bram Moolenaar
Patch 7.3.299 Problem:Source code not in Vim style. Solution: Adjust the style. (Elias Diem) Files: src/gui_photon.c *** ../vim-7.3.298/src/gui_photon.c 2011-09-07 18:58:24.0 +0200 --- src/gui_photon.c2011-09-07 19:02:59.0 +0200 *** *** 535,547

Patch 7.3.300

2011-09-07 Fir de Conversatie Bram Moolenaar
Patch 7.3.300 Problem:Python doesn't parse multi-byte argument correctly. Solution: Use t instead of s. (lilydjwg) Files: src/if_py_both.h *** ../vim-7.3.299/src/if_py_both.h 2011-07-07 15:08:53.0 +0200 --- src/if_py_both.h2011-09-07 19:25:12.0 +0200

Patch 7.3.301

2011-09-07 Fir de Conversatie Bram Moolenaar
Patch 7.3.301 Problem:When 'smartindent' and 'copyindent' are set a Tab is used even though 'expandtab' is set. Solution: Do not insert Tabs. Add a test. (Christian Brabandt) Files: src/misc1.c, src/testdir/test19.in, src/testdir/test19.ok *** ../vim-7.3.300/src/misc1.c

Re: Bug in 7.3.301: 'modified' not set when buffer changed by BufRead autocommand

2011-09-07 Fir de Conversatie James Vega
On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote: When a buffer is modified by a BufRead autocommand or by a filetype plugin, 'modified' is not set. This is documented in the text below :help gzip-example. The commands executed for the BufNewFile, BufRead/BufReadPost,

Re: Bug in 7.3.301: 'modified' not set when buffer changed by BufRead autocommand

2011-09-07 Fir de Conversatie Gary Johnson
On 2011-09-07, James Vega wrote: On Wed, Sep 07, 2011 at 02:16:59PM -0700, Gary Johnson wrote: When a buffer is modified by a BufRead autocommand or by a filetype plugin, 'modified' is not set. This is documented in the text below :help gzip-example. The commands executed for the