Martin Stjernholm <mast@...> writes:
> David Abrahams <dave@...> wrote:
>> Martin Stjernholm <mast@...> writes:
>> > David Abrahams <dave@...> wrote:
>> >> I'm sure you want some more-detailed info; just let me know and I'll
>> >> turn on whatever you like.
>> >> -----
>> >> c-guess-basic-syntax: Invalid function: (macro lambda (&optional limit) "Backward skip over syntactic whitespace.
>> >> Syntactic whitespace is defined as whitespace characters, comments,
>> >> and preprocessor directives. However if point starts inside a comment
>> >> or preprocessor directive, the content of it is not treated as
>> >> whitespace.
>> >> LIMIT sets a lower limit of the backward movement, if specified. If
>> >> LIMIT is reached inside a line comment or preprocessor directive then
>> >> the point is moved into it past the whitespace at the end.
>> >> Note that this function might do hidden buffer changes. See the
>> >> comment at the start of cc-engine.el for more info." (if limit (\`
>> >> (save-restriction (narrow-to-region (or (\, limit) (point-min))
>> >> (point-max)) (c-backward-sws))) (quote (c-backward-sws))))
>> > It looks like the macro `c-backward-syntactic-ws' wasn't defined when
>> > some other file was compiled. That's typically a sign that the correct
>> > version of cc-defs.el (which contains most macros) wasn't loaded then.
>> > I thought I had safeguards to avoid that. How did you compiled it?
>> > What other version(s) of CC Mode do you have in your load-path?
>> I'm sorry, Martin, despite apparently having the entire message thread
>> in GNUs I don't know exactly what problem we were talking about.
> Well, afaict this is a separate problem from the rest of the
Yeah, that's what it looks like to me also.
> I have no more relevant info that isn't covered by the citations
Me neither. Strange; it seems to come from out of nowhere.
>> Did you solve those hanging problems that we were discussing? I
>> could try cc-mode again...
> Yes, the one I'm aware of, at least. You've tested with the fix and
> did not report another hang. You have however reported on the
> indentation of multiline templates, an issue I'll probably get back to
> you on.
Yes. Well, I'd be very pleased if we could get those to indent
automatically in the particular quirky style my colleagues and I are
using. Some of the principles:
1. Closing angle brackets line up with the template name that opens
2. No endline layout. If you write an open paren/bracket/brace and can't fit the
matching close on the same line, you must break the line after the
open element. Not:
3. operators and commas that continue lines appear after the newline:
There's a bit more to it; as I mentioned earlier something
approximating the full rules can be found in the gSTLFilt.pl script
Thanks for your attention,