I've been assisting a colleague with their C code, and he has
learned to add semicolons at the end of statements too well. His
current favourite mistake is to write
if (expression == value);
{
do_something();
};
I frequently miss the trailing semicolon on the first line. So I
was wonde
thing now is that I'm getting the ; in for
loops showing up as red, when the rest is cleared by fixing the
syntax.
for(k=0;k On 22/02/11 1:23 AM, Hugh Sasse wrote:
> > I've been assisting a colleague with their C code, and he has
> > learned to add semicolons at the end o
On Tue, 22 Feb 2011, Ben Schmidt wrote:
> It was mostly copy and paste. I just had to know where to steal it from. :-)
>
> Add this:
>
> syn cluster cParenGroup add=cSemiError
>
Thank you, that's fixed it.
To save anyone the problem with long lines in email, here it is in base64:
c3luI
On Tue, 22 Feb 2011, Dominique Pellé wrote:
> On Hugh Sasse wrote:
>
> > I've been assisting a colleague with their C code, and he has
> > learned to add semicolons at the end of statements too well. His
> > current favourite mistake is to write
On Tue, 22 Feb 2011, Charles E Campbell Jr wrote:
> Just eyeballing it; may I suggest changing
>
> syn regioncIfmatchgroup=cConditional start=+if ...
>
> to
>
> syn regioncIfmatchgroup=cConditional start=+\
> Regards,
> Chip Campbell
>
Hugh
--
You received th
On Sat, 26 Feb 2011, howard Schwartz wrote:
> I know my pleas are getting old for you veterans. But I am trying to make
Only rejoined the list recently, but searching doesn't show up any replies
to your messages about this.
> .viminfo work for a blind friend, and he keeps getting more and more e
On Wed, 2 Mar 2011, Jan Larres wrote:
>
> Also, Comic Sans?! WHY?!? Poor Vim.
I don't know in this case, but someone teaching staff about dyslexia
said it is one of the easiest fonts [typefaces?] for dyslexics to read.
>
> Jan
Hugh
--
You received this message from the "vim_use" m
On Wed, 2 Mar 2011, Schorschie wrote:
> Hello Forum,
>
> I'm quite new here, so I'm not familiar with your etiquette yet. I can
> indtroduce myself later if you want.
>
> I'm currently comparing a lot of text*) so I was wondering weather
> there is something wich finds me blocks of similar text
On Wed, 2 Mar 2011, kuru wrote:
> Hi
>
> Currently when ever I open .c files, "//" comment lines show up as
> "errors" based on the color syntax. I have tried the latest c.vim from
> last November which seems to resolve the issue but that one is
> relatively shorter and not as extended as the pre
On Thu, 3 Mar 2011, Sapfeer wrote:
> Dear all,
>
> I want to create a command that will insert comment mark, for instance '#',
> space, date and time on the next line after current, but AFAICS there is no
> way to put insert commands like *o* in command. The most obvious way - use
> mapping, but
On Fri, 4 Mar 2011, howard Schwartz wrote:
> > What I meant was that Vim is now at version 7.3.138. You apparently
> > are using 7.3.0. This is probably OK--I do not see any bug fixes
> > related to screen drawing or special keys--but you are missing out on
> > a lot of bug fixes and minor feature
11 matches
Mail list logo
