GNU bug report logs - #21517
11.88.8; Error parsing wrong in Plain TeX mode

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21517 in the body.
You can then email your comments to 21517 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: bug-auctex <at> gnu.org
Subject: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 10:38:34 +0200

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.

The following Plain TeX source:

\underline{A}%
\bye

generates as expected errors in the log:

-------------------- log file
This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015) (preloaded format=pdfetex 2015.9.14)  19 SEP 2015 10:23
entering extended mode
 restricted \write18 enabled.
 %&-line parsing enabled.
**\input bugauctex.tex
(./bugauctex.tex
! Missing $ inserted.
<inserted text> 
                $
<to be read again> 
                   \underline 
l.2 \underline
              {A}%
I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.

! Missing $ inserted.
<inserted text> 
                $
<to be read again> 
                   \par 
\bye ->\par 
            \vfill \supereject \end 
l.3 \bye
        
I've inserted a begin-math/end-math symbol since I think
you left one out. Proceed, with fingers crossed.
-------------------- end of extract of log file

I see in the message mini-buffer
> TeX errors in `*~/_texlatex/1509/bugauctex output*'. Use C-c ` to display.

On C-c `, I get:
> No more errors.

Then I go to Error Overview in the Command menu, and I get:
> TeX-error-overview: No errror or warning to show

I am reporting this today, but noticed it
since a long time (I don't know since when)

Enabled minor modes: Auto-Composition Auto-Compression Auto-Encryption
Auto-Fill Blink-Cursor Column-Number Delete-Selection File-Name-Shadow
Font-Lock Global-Font-Lock Line-Number Mac-Mouse-Wheel Menu-Bar Shell-Dirtrack
Tex-Pdf Tool-Bar Tooltip Transient-Mark

(Information about these minor modes follows the major mode info.)

TeX/P mode defined in `tex-mode.el':
:override advice: `TeX-plain-tex-mode'

Is this actually the AUCTeX plain TeX mode ?

I activated the mode via C-cC-n after entering in the buffer the two
lines
\underline{A}%
\bye

Best,

Jean-Francois
------------------------------------------------------------------------
Emacs  : GNU Emacs 24.5.6 (x86_64-apple-darwin13.4.0, Carbon Version 157 AppKit 1265.21)
 of 2015-08-26 on Atago.local
Package: 11.88.8

current state:
==============
(setq
 AUCTeX-date "2015-08-28"
 window-system 'mac
 LaTeX-version "2e"
 TeX-style-path '("~/.emacs.d/auctex"
		  "/Users/XXXXXXXX/.emacs.d/elpa/auctex-11.88.8/style"
		  "/Users/XXXXXXXX/.emacs.d/auctex/auto"
		  "/Users/XXXXXXXX/.emacs.d/auctex/style" "auto" "style")
 TeX-auto-save t
 TeX-parse-self t
 TeX-master t
[snip]
)

Message #8 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: 21517 <at> debbugs.gnu.org
Subject: bug#21517: (11.88.8; Error parsing wrong in Plain TeX mode)
Date: Sat, 19 Sep 2015 11:22:00 +0200

> 
> Then I go to Error Overview in the Command menu, and I get:
>> TeX-error-overview: No errror or warning to show
> 

forgot to point out the typo above ("errror") in the AUCTeX message

best

Jean-Francois

Message #11 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: Tassilo Horn <tsdh <at> gnu.org>
To: jfbu <jfbu <at> free.fr>
Cc: 21517 <at> debbugs.gnu.org
Subject: Re: bug#21517: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 14:03:29 +0200

jfbu <jfbu <at> free.fr> writes:

Hi!

> The following Plain TeX source:
>
> \underline{A}%
> \bye
>
> generates as expected errors in the log:
>
> -------------------- log file
> (./bugauctex.tex
> ! Missing $ inserted.
> <inserted text> 
> -------------------- end of extract of log file
>
> I see in the message mini-buffer
>> TeX errors in `*~/_texlatex/1509/bugauctex output*'. Use C-c ` to display.
>
> On C-c `, I get:
>> No more errors.

Ah, there's been a bug in `TeX-TeX-sentinel' which invoked error parsing
only if there were no errors. ;-)

I think it is fixed now.  Could you please check and report back?

Bye,
Tassilo

Message #14 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: Tassilo Horn <tsdh <at> gnu.org>
To: jfbu <jfbu <at> free.fr>
Cc: 21517 <at> debbugs.gnu.org
Subject: Re: bug#21517: (11.88.8; Error parsing wrong in Plain TeX mode)
Date: Sat, 19 Sep 2015 14:04:16 +0200

jfbu <jfbu <at> free.fr> writes:

>> Then I go to Error Overview in the Command menu, and I get:
>>> TeX-error-overview: No errror or warning to show
>
> forgot to point out the typo above ("errror") in the AUCTeX message

That's also fixed now, well, even before the actual error.

Bye,
Tassilo

Message #17 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: 21517 <at> debbugs.gnu.org
Cc: Tassilo Horn <tsdh <at> gnu.org>
Subject: Re: bug#21517: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 14:15:43 +0200

Hi Tassilo

Le 19 sept. 2015 à 14:03, Tassilo Horn <tsdh <at> gnu.org> a écrit :

>> 
>> I see in the message mini-buffer
>>> TeX errors in `*~/_texlatex/1509/bugauctex output*'. Use C-c ` to display.
>> 
>> On C-c `, I get:
>>> No more errors.
> 
> Ah, there's been a bug in `TeX-TeX-sentinel' which invoked error parsing
> only if there were no errors. ;-)
> 
> I think it is fixed now.  Could you please check and report back?


Yes, I applied the patch to tex-buf.el from the latest commit
and error parsing seems to function as expected in TeX-mode

C-c `  is OK, and Command->Error Overview also

this is at least on my \underline example, but as I never do any
error in TeX coding if not intentionally, it might be
a very long time before I can confirm more generally, though 

;-)

Thanks for the quick fix,

Best,
Jean-François

Message #20 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: Tassilo Horn <tsdh <at> gnu.org>
Cc: 21517 <at> debbugs.gnu.org
Subject: Re: bug#21517: (11.88.8; Error parsing wrong in Plain TeX mode)
Date: Sat, 19 Sep 2015 14:17:21 +0200

Le 19 sept. 2015 à 14:04, Tassilo Horn <tsdh <at> gnu.org> a écrit :

> jfbu <jfbu <at> free.fr> writes:
> 
>>> Then I go to Error Overview in the Command menu, and I get:
>>>> TeX-error-overview: No errror or warning to show
>> 
>> forgot to point out the typo above ("errror") in the AUCTeX message
> 
> That's also fixed now, well, even before the actual error.
> 
> Bye,
> Tassilo

noted, thanks again.

Bye,

Jean-François

Message #23 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: Mosè Giordano <mose <at> gnu.org>
To: jfbu <jfbu <at> free.fr>
Cc: 21517 <at> debbugs.gnu.org, Tassilo Horn <tsdh <at> gnu.org>
Subject: Re: bug#21517: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 16:42:19 +0200

Hi Jean-François,

2015-09-19 14:15 GMT+02:00 jfbu <jfbu <at> free.fr>:
> Hi Tassilo
>
> Le 19 sept. 2015 à 14:03, Tassilo Horn <tsdh <at> gnu.org> a écrit :
>
>>>
>>> I see in the message mini-buffer
>>>> TeX errors in `*~/_texlatex/1509/bugauctex output*'. Use C-c ` to display.
>>>
>>> On C-c `, I get:
>>>> No more errors.
>>
>> Ah, there's been a bug in `TeX-TeX-sentinel' which invoked error parsing
>> only if there were no errors. ;-)
>>
>> I think it is fixed now.  Could you please check and report back?
>
>
> Yes, I applied the patch to tex-buf.el from the latest commit
> and error parsing seems to function as expected in TeX-mode

Oops, sorry, I think those bugs were my fault, thanks for having
spotted them!

> C-c `  is OK, and Command->Error Overview also
>
> this is at least on my \underline example, but as I never do any
> error in TeX coding if not intentionally, it might be
> a very long time before I can confirm more generally, though

I wonder how many plain TeX users we have (or at least plain TeX users only,
no LaTeX, who care to report bugs): bug fixed with commit

    * 1a5d447 (2013-04-17)  Fix plain TeX abbrev table name.

(http://git.savannah.gnu.org/gitweb/?p=auctex.git;a=commitdiff;h=1a5d447)
made opening plain TeX files pretty uncomfortable, still was never
reported before the fix, which came 2.5 years after the bug had been
introduced and 5 months after previous stable version.

Bye,
Mosè

Message #26 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: jfbu <jfbu <at> free.fr>
To: Mosè Giordano <mose <at> gnu.org>
Cc: 21517 <at> debbugs.gnu.org, Tassilo Horn <tsdh <at> gnu.org>
Subject: Re: bug#21517: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 17:08:18 +0200

Le 19 sept. 2015 à 16:42, Mosè Giordano <mose <at> gnu.org> a écrit :

> Hi Jean-François,
> 
> 2015-09-19 14:15 GMT+02:00 jfbu <jfbu <at> free.fr>:
>> Hi Tassilo
>> 
>> Le 19 sept. 2015 à 14:03, Tassilo Horn <tsdh <at> gnu.org> a écrit :
>> 
>>>> 
>>>> I see in the message mini-buffer
>>>>> TeX errors in `*~/_texlatex/1509/bugauctex output*'. Use C-c ` to display.
>>>> 
>>>> On C-c `, I get:
>>>>> No more errors.
>>> 
>>> Ah, there's been a bug in `TeX-TeX-sentinel' which invoked error parsing
>>> only if there were no errors. ;-)
>>> 
>>> I think it is fixed now.  Could you please check and report back?
>> 
>> 
>> Yes, I applied the patch to tex-buf.el from the latest commit
>> and error parsing seems to function as expected in TeX-mode
> 
> Oops, sorry, I think those bugs were my fault, thanks for having
> spotted them!
> 
>> C-c `  is OK, and Command->Error Overview also
>> 
>> this is at least on my \underline example, but as I never do any
>> error in TeX coding if not intentionally, it might be
>> a very long time before I can confirm more generally, though
> 
> I wonder how many plain TeX users we have (or at least plain TeX users only,
> no LaTeX, who care to report bugs): bug fixed with commit
> 
>    * 1a5d447 (2013-04-17)  Fix plain TeX abbrev table name.
> 
> (http://git.savannah.gnu.org/gitweb/?p=auctex.git;a=commitdiff;h=1a5d447)
> made opening plain TeX files pretty uncomfortable, still was never
> reported before the fix, which came 2.5 years after the bug had been
> introduced and 5 months after previous stable version.
> 
> Bye,
> Mosè

Hi Mosè, 

I couldn't tell, but I suspect I completely under-estimate the
benefits I would get from AUCTeX. There must be tons of features
I don't use (exactly like with Emacs globally: every few years
I want to learn more, I do, then I forget and I am back to
beginner level; finally the only truly important moments
were when I did for the very first time the tutorial
and learned C-xC-s, C-x-C-c. Another big moment must have been
years later when I started having an Emacs on a Mac OS,
and understood that say C-M-s (whatever it does) was to be
keyed in Escape then a fraction of a second later CTRL-s. 
Those were important steps because I did them only once
and I recalled the lesson; in later years though everything
I ever learn is quickly completely forgotten. End of long digression)
For example there must be some automatic completion
but I just never use such things. 

Thus, when some features go awry, I can certainly stay years
without becoming aware.

Many years back my relation with AUCTeX was more like a fight:
for example how to get it NOT to modify a .tex source file
by the automatic addition of local file variables at the end
when opening it in a buffer. As a novice, it took me quite
a while to identify the proper magic, what was it, let's
dig in my .emacs, ah yes

(setq TeX-one-master '"\"<none>\"")

that was quite a feat getting the suitable escaping and quotes
back then, I was so young and tender. These must have been
before the Google arose. And naturally I didn't have internet
at home.

Then I developed a bad relationship with the install script of the
release tarballs, which had IIRC a tendency to
put things in my /usr/local (or somewhere else) that I didn't want.
Anyway,
that's all past, gone and forgotten. I use ELPA, and that's it.

And I am very glad !

Coming back with more focus on the topic, I don't do much
typesetting with Plain TeX these days, but use it when I need
to quickly check some macros (obviously not from LaTeX packages).

Bug reporting is not always such a nice experience, contrarily
to what I enjoy with Tassilo and yourself since some time now.

Sometimes one has a situation which other people don't understand
because they are not on the same system. Thus I had a very
hard time getting the TeX Live people understand their
kpsewhich has a major speed problem on Mac OS X under certain
circumstances.

Thus I take this opportunity to thank you Mosè, and Tassilo
for all your responsiveness in handling user reports,

bye

Jean-François




 

Message #29 received at 21517 <at> debbugs.gnu.org (full text, mbox):

From: David Kastrup <dak <at> gnu.org>
To: jfbu <jfbu <at> free.fr>
Cc: 21517 <at> debbugs.gnu.org, Mosè Giordano <mose <at> gnu.org>,
 Tassilo Horn <tsdh <at> gnu.org>
Subject: Re: bug#21517: 11.88.8; Error parsing wrong in Plain TeX mode
Date: Sat, 19 Sep 2015 17:25:05 +0200

jfbu <jfbu <at> free.fr> writes:

> Another big moment must have been
> years later when I started having an Emacs on a Mac OS,
> and understood that say C-M-s (whatever it does) was to be
> keyed in Escape then a fraction of a second later CTRL-s.

More like a fraction of an hour.  The timing is only critical on serial
line ASCII terminals where the cursor keys create some sequence starting
with ESC.  In that case only, you should _not_ followup an ESC
immediately with a (or so) if you wanted to key in M-a but instead wait
a tiny moment (read-key-delay I think).

-- 
David Kastrup

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.