This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".
The branch, master has been updated
via 8cd9b0d0af151ffb235c88510b9ab5a8ef25fc2b (commit)
from
Hi Arash,
2015-11-28 18:38 GMT+01:00 Arash Esbati :
> Hi Tassilo,
>
> Tassilo Horn writes:
>
>> Arash Esbati writes:
>>
>>> please find attached 4 patch sets containing:
>>>
>>> * Makefile.in (STYLESRC): Add new style.
>>>
>>> * style/ntheorem.el: New
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".
The branch, master has been updated
via 8cd9b0d0af151ffb235c88510b9ab5a8ef25fc2b (commit)
from
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
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
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
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
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
FYI, I will not do this work soon...
Now, concerning Eric's question about auto-completion, I do not intend to
reinvent the wheel. I will reuse whatever autocompletion mechanism is
provided by BBDB of with which BBDB has some already existing
connection. Well, my intention is plainly to use
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
Hi
I know this is a bit off topic, since bibtex.el is not part of auctex.
However I would like to hear your opinion. As I said earlier I am
switching form Xemacs to GNU emacs.
So far I have not seen any dramatic difference with bibtex.el till now.
Xemacs still uses an almost attic version from
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:
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,
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,
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
>
>
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".
The branch, master has been updated
via 2880b625ce09cc86ac168530cdc23fc2e3e91ad9 (commit)
from
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU AUCTeX".
The branch, master has been updated
via 2880b625ce09cc86ac168530cdc23fc2e3e91ad9 (commit)
from
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.
18 matches
Mail list logo