[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-AUCTeX] Re: 2007-04-16; Bad highlighting

From: Andreas Matthias
Subject: [Bug-AUCTeX] Re: 2007-04-16; Bad highlighting
Date: Sat, 21 Apr 2007 13:52:50 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

Ralf Angeli wrote:

> * David Kastrup (2007-04-20) writes:
>> \newcommand\blubb[1]
>> {%
>>   \bla
>> }
> [...]
>> the "\bla" will be highlighted as if it were the defined macro.
>> Actually, the whole content of \blubb gets highlighted in that manner.
> It's an argument of \newcommand, so the color used for arguments is
> applied.  This is the intended behavior you are observing.

Yes, \newcommand is not a primitive. But most of the time I'm
thinking of \newcommand as an (equal) replacement of \def. That's
why I would expect both \def and \newcommand to have the same

Apart from that, the highlighting as an argument slows down my
emacs tremendous. It might not be good programming practice to
have macros (\newcommands) with more the 100 lines. Nevertheless,
I have. When scrolling up and down while point is in such long
arguments I get the impression that emacs really has to ponder
what to do.

Reading long arguments is a nuisance when everything is highlighted
the same way. Last time I had to edit a very long \newcommand I replace
\newcommand with \def for the time of editing.

I would prefer if \newcommand would be treated as \def.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]