Re: C formatter

2015-07-07 Fir de Conversatie h_east
Hi Don, 2015-7-7(Tue) 22:34:37 UTC+9 Don: > The C formatter re-indents multi-line strings. This is incorrect in my > opinion, introducing potentially long strings of white-space where it > was not intended and where it matters (unlike in code). Indeed. I think so too. BTW, If you can modify this

Re: colorcolumn/cursorcolumn conceal + wrap voodoo

2015-07-07 Fir de Conversatie Dominique Pellé
Christian Brabandt wrote: > Hi Bram! > > On Di, 07 Jul 2015, Bram Moolenaar wrote: > >> Christian, since you worked in this area for the linebreak stuff, can >> you check if this patch improves things? > > I am currently short on time and have to fix the visual increment > feature, so I can't loo

Re: Patch 7.4.757

2015-07-07 Fir de Conversatie h_east
Hi Bram, 2015-7-8(Wed) 2:08:03 UTC+9 Bram Moolenaar: > Hirohito Higashi wrote: > > > Hi Bram, Anatol and Vim developers! > > > > 2015-7-7(Tue) 8:20:43 UTC+9 Anatol Pomozov: > > > Is HEAD vim revision still broken? Could developers loos at this > > > bug? Many Arch developers report this issue an

Re: colorcolumn/cursorcolumn conceal + wrap voodoo

2015-07-07 Fir de Conversatie Christian Brabandt
Hi Bram! On Di, 07 Jul 2015, Bram Moolenaar wrote: > Christian, since you worked in this area for the linebreak stuff, can > you check if this patch improves things? I am currently short on time and have to fix the visual increment feature, so I can't look at it before the end of the week (or e

Proposal: Generalization of automatic update of timestamps in lines like "Last Change: 2015-07-07"

2015-07-07 Fir de Conversatie Roland Eggner
Hi all In my vimrc the BufRead autocommands for some filetypes call this function. Maybe some readers want to “copy & paste” or even enhance it (the vim license applies): function! s:UpdateTimestamp(RegexMatchingLine, TimestampFormat) " File is left untouched, update of timestamp dropped,

Re: Proposal: fixing "Todo" highlighting chaos

2015-07-07 Fir de Conversatie Roland Eggner
Hi Jean-François On 2015-07-06 Monday at 14:16 -0700 Jean-François Bignolles wrote: > Using different languages, I remarked that the "Todo" system (highlighting > of special words inside comments) was currently a bit chaotic: some keywords > are highlighted for one syntax, but not for an another

Re: colorcolumn/cursorcolumn conceal + wrap voodoo

2015-07-07 Fir de Conversatie Bram Moolenaar
Alexey Radkov wrote: > Finally I made a patch that fixes multiple wrapping breaks too. It should > not affect badly all the features elaborated in win_line() so far, > including Tab adjustments / boguscols. See attached movie. > > Cheers, Alexey. > > 2015-07-07 14:49 GMT+03:00 Alexey Radkov : >

Re: Patch 7.4.757

2015-07-07 Fir de Conversatie Bram Moolenaar
Hirohito Higashi wrote: > Hi Bram, Anatol and Vim developers! > > 2015-7-7(Tue) 8:20:43 UTC+9 Anatol Pomozov: > > Is HEAD vim revision still broken? Could developers loos at this > > bug? Many Arch developers report this issue and we would like to > > release working version of vim. > > I think

C formatter

2015-07-07 Fir de Conversatie Donald Allen
The C formatter re-indents multi-line strings. This is incorrect in my opinion, introducing potentially long strings of white-space where it was not intended and where it matters (unlike in code). /Don Allen -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your

Re: colorcolumn/cursorcolumn conceal + wrap voodoo

2015-07-07 Fir de Conversatie Alexey Radkov
Looks like I managed to fix this (not completely, see below). The idea is that part of win_line() starting from line else if (wp->w_p_cole > 0 && is_concealing) and including that "voodoo" code for wrapped lines increments value of vcol_off. Doing that for vcol_off but not fot vcol is ok for lin

Issue 379 in vim: vimscript's own syntax highlighter ignores line continuations

2015-07-07 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 379 by anntzer@gmail.com: vimscript's own syntax highlighter ignores line continuations https://code.google.com/p/vim/issues/detail?id=379 What steps will reproduce the problem? Highlight the following source with vim's