Hi Mosè
Le 03/12/2015 00:32, Mosè Giordano a écrit :
Hi Jean-François,
2015-11-30 17:09 GMT+01:00 jfbu :
Le 30 nov. 2015 à 16:55, Mosè Giordano a écrit :
2015-11-30 16:51 GMT+01:00 jfbu :
State : CHANGED outside Customize.
Usually you have this state for a variable set(q) manually i
Hi Jean-François,
2015-11-30 17:09 GMT+01:00 jfbu :
>
> Le 30 nov. 2015 à 16:55, Mosè Giordano a écrit :
>
>> 2015-11-30 16:51 GMT+01:00 jfbu :
>>>State : CHANGED outside Customize.
>>
>> Usually you have this state for a variable set(q) manually in the init
>> file. Is this your case?
>
> n
Le 30 nov. 2015 à 16:55, Mosè Giordano a écrit :
> 2015-11-30 16:51 GMT+01:00 jfbu :
>>State : CHANGED outside Customize.
>
> Usually you have this state for a variable set(q) manually in the init
> file. Is this your case?
no, I don't.
actually there is (forgetting my earlier big confus
Hi All,
sorry about this message, I misread the lisp syntax and
I had forgotten that five minutes ago I had re-customized
the thing for its default value.
apologies for the confusion
Jean-François
Le 30/11/2015 16:51, jfbu a écrit :
Le 30/11/2015 16:36, jfbu a écrit :
or rather
LaTeX-fill-b
2015-11-30 16:51 GMT+01:00 jfbu :
> State : CHANGED outside Customize.
Usually you have this state for a variable set(q) manually in the init
file. Is this your case?
Bye,
Mosè
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/l
Le 30/11/2015 16:36, jfbu a écrit :
or rather
LaTeX-fill-break-at-separators to nil, as this is a part
of the file where standard LaTeX syntax is somewhat tortured.
Hi Mosè,
I have another issue here. I customized
LaTeX-fill-break-at-separators unchecking in the customize buffer
all check boxe
Le 30/11/2015 15:43, Mosè Giordano a écrit :
is seen as a single paragraph. Probably something like
"[\n\t][ \t]*%*[ \t]*[\n\r]"
would be better, but this hard-codes "%" as comment sign, and I don't
know if fixes the concrete problem encountered by Jean-François.
Hi Mosè and Marcin
Yes
Hi Marcin,
2015-11-30 14:48 GMT+01:00 Marcin Borkowski :
> I have to finally analyse your patch to the bug we talked about (sorry
> for my terrible delay!),
Don't worry, take your time ;-)
> but let me chime in again here, since I've
> studied large parts of texmathp recently.
Good :-)
> The o
On 2015-11-30, at 14:32, Mosè Giordano wrote:
> 2015-11-30 12:55 GMT+01:00 jfbu :
>> I had to grab 354 lines before the offending location to find an isolated
>> $ which confuses AUCTeX.
>>
>> Although all the intervening macro definitions never define a paragraph,
>> there were a few paragraphs
2015-11-30 12:55 GMT+01:00 jfbu :
> I had to grab 354 lines before the offending location to find an isolated
> $ which confuses AUCTeX.
>
> Although all the intervening macro definitions never define a paragraph,
> there were a few paragraphs inside the intervening comments
>
> Hence it seems that
Hi, just my 2 cents...
On 2015-11-30, at 12:55, jfbu wrote:
> I never ever used \(...\) ...
I use them all the time.
> Recently I saw unanimous reproval on SE of a poor innocent bystander's
> proposal to to use $$$ ... $$$ as shortcut for amsmath's align
Horrible idea indeed, those triple dol
Le 30/11/2015 12:18, Mosè Giordano a écrit :
Hi Jean-François,
2015-11-30 11:46 GMT+01:00 jfbu :
Hi,
I know this has been discussed prior to 11.88.9 release, but I have
a confusing problem when the same source behaves differently in two
files under the same docTeX mode
\documentclass{art
Hi Jean-François,
2015-11-30 11:46 GMT+01:00 jfbu :
> Hi,
>
> I know this has been discussed prior to 11.88.9 release, but I have
> a confusing problem when the same source behaves differently in two
> files under the same docTeX mode
>
>
> \documentclass{article}% same with scrdoc
>
> \begin
Hi,
I know this has been discussed prior to 11.88.9 release, but I have
a confusing problem when the same source behaves differently in two
files under the same docTeX mode
\documentclass{article}% same with scrdoc
\begin{document}
% Test $char37 $space added note on the implementation:
%
14 matches
Mail list logo
