auctex
[Top][All Lists]
Advanced

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

Re: [AUCTeX] Re: problem (bug?) with fill prefix in latex mode


From: Ralf Angeli
Subject: Re: [AUCTeX] Re: problem (bug?) with fill prefix in latex mode
Date: Sat, 17 Oct 2009 13:48:14 +0200

* Martin Rubey (2009-10-16) writes:

> I should add: the problem is very likely in LaTeX-fill-paragraph from
> latex.el from auctex, therefore I CC...
>
> The top lines of the ChangeLog in /usr/share/emacs/site-lisp/auctex/ say
>
> 2007-01-12  Ralf Angeli  <address@hidden>
>
>    * Version 11.84 released.
>
> (No idea how to get the version otherwise)

C-h v AUCTeX-version <RET>

> I'm using emacs 22 there.
>
> Martin
>
> Martin Rubey <address@hidden> writes:
>
>> I have the following text in a latex mode buffer
>>
>>       ++ maxMixedDegree(d) specifies the maximum q-degree of the
>>       ++ coefficient polynomials in a recurrence with polynomial
>>       ++ coefficients, in the case of mixed shifts.  Although slightly
>>       ++ inconsistent, maxMixedDegree(0) specifies that no mixed shifts
>>       ++ are allowed. This option is expressed in the form
>>       ++ \spad{maxMixedDegree == d}.
>>
>>
>> setting fill-prefix to "      ++ " and pressing M-q turns it into
>>
>>       ++ maxMixedDegree(d) specifies the maximum q-degree of the ++
>>       coefficient polynomials in a recurrence with polynomial ++
>>       coefficients, in the case of mixed shifts.  Although slightly
>>       ++ inconsistent, maxMixedDegree(0) specifies that no mixed
>>       shifts ++ are allowed. This option is expressed in the form ++
>>       \spad{maxMixedDegree == d}.
>>
>> Help for fixing that would be greatly appreciated!

The filling and indentation code in latex.el tries hard to support outer
and inner indentation of commented passages of text.  It seems the
handling of fill prefixes broke when I implemented this feature.

You can get some better results by activating Adaptive Fill mode and
adding "+" to `adaptive-fill-regexp'.  The problem remaining with this
approach is an excessive blank after the fill prefix which is not taken
care of by the indentation code.

-- 
Ralf




reply via email to

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