auctex-devel
[Top][All Lists]
Advanced

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

Re: [AUCTeX-devel] Feature request for docTeX mode: extend \changes and


From: Tassilo Horn
Subject: Re: [AUCTeX-devel] Feature request for docTeX mode: extend \changes and \begin{macro}...\end{macro}
Date: Mon, 04 Mar 2013 10:33:43 +0100
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (gnu/linux)

David Kastrup <address@hidden> writes:

Hi!

>> 1st date-default of \changes:
>> docTeX mode offers support for \changes macro. When C-m chan RET asks
>> for the date, it would be nice to have the current date instead of
>> the empty one to be the default.
>
> Sounds reasonable, though the format should likely be 2013/02/28
> instead of whatever local date, right?

I've just implemented that, so now you get today as the default value
for \changes (and also \date).

>> 2nd \end{macro} with additional comment:
>> I often have constructs like:
>>
>>   % \begin{macro}{\foo1}
>>   ...
>>   % \begin{macro}{\foo2}
>>   ...
>>   % \end{macro}
>>   % \begin{macro}{\foo3}
>>   ...
>>   % \begin{macro}{\foo4}
>>   ...
>>   % \end{macro}
>>   % \end{macro}
>>   % \end{macro}
>>
>> The ... may be several dozens of lines and many more pairs of
>> \begin{macro}...  \end{macro} may be nested. In such cases, it is
>> often not easy to see, which \end{macro} corresponds with which
>> \begin{macro}. Therefore I usually use:
>>
>>   % \begin{macro}{\foo1}
>>   ...
>>   % \begin{macro}{\foo2}
>>   ...
>>   % \end{macro}^^A \foo2
>>   % \begin{macro}{\foo3}
>>   ...
>>   % \begin{macro}{\foo4}
>>   ...
>>   % \end{macro}^^A \foo4
>>   % \end{macro}^^A \foo2
>>   % \end{macro}^^A \foo1
>>
>> It would be nice, if auxtex would add the "^^A \..." comment on it's own, 
>> while using C-e macro RET. Same for environment "environment".
>
> I quite disagree here since such comments tend to become out of sync
> with reality when changing materials.  Instead, AUCTeX should
> calculate and display (in an unobtrusive manner/place) the respective
> information on the fly and not place it in the buffer.

Yes, that sounds preferrable.  Or something like `blink-matching-paren'
for environments.  Patches welcome.

Bye,
Tassilo




reply via email to

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