Re: forward-comment doesn't (quite) match its documentation

[Stefan Monnier]

>>>>> "Alan" == Alan Mackenzie <none@example.invalid> writes:
> It doesn't indent properly - if an awk statement isn't terminated by a
> ';' (and they usually aren't), the next statement is treated as a
> continuation, and indented a further n columns.  This makes it unusable,
> and has been complained about quite a lot on comp.lang.awk.

Yes, we know about those ;-)

> I presume that at one time, awk-mode was fine, but as c-mode was
> gradually enhanced, awk-mode got left behind.

Oh, so you presume it got worse.  I rather think that it never worked.
But I have no evidence and it doesn't really matter, anyway, so let's move on.

>> Are you working on the version that's in the CVS repository ?  If not,
>> you should.
> Yes, with the approval of and under the guidance of Martin Stjernholm,
> cc-mode's maintainer.  The bulk of the changes will be within the cc-mode

Excellent.

>> The version that's in the CVS repository has font-lock tricks to 
>> (try to) take care of it.
> They're not yet perfect:  For example, in a statement like:
> /^[ \t]*#/ {comments += 1}

Huh?  I just tried it and it worked fine.  The /.../ part is highlighted
with the font-lock-string text property and the rest as plain code.

Are you sure you tried with the version that's in the trunk of
the CVS repository ?

> At the moment I'm planning on setting the syntax-table text property on
> certain awkward characters ('/' when it's a division sign, and possibly

That's exactly what my font-lock settings do.


        Stefan