Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-05 Thread Ralf Angeli
* Stefan Vollmar (2007-07-05) writes:

 Dear Ralf,

 Am 04.07.2007 um 23:12 schrieb Ralf Angeli:

 Judging by the general quality (again: I have only scratched the
 surface of all the beautiful and powerful features) of a reportedly
 mature tool like AUCTeX this must be the case - because otherwise
 people would have that kind of problem all the time.

 It's likely more a case of people not using the feature.

 This touches the last question of my previous posting: so  
 (experienced?) users of AUCTeX simply have other (better?) ways of  
 debugging their TeX code than using TeX-next-error?

Or they do not read the documentation and are not aware of the feature.

-- 
Ralf


___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex


Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-04 Thread Ralf Angeli
* Stefan Vollmar (2007-07-04) writes:

 That raises the following questions: Is my example especially ugly/ 
 difficult? And why so?

It's not especially ugly or difficult.

 Judging by the general quality (again: I have only scratched the  
 surface of all the beautiful and powerful features) of a reportedly  
 mature tool like AUCTeX this must be the case - because otherwise  
 people would have that kind of problem all the time.

It's likely more a case of people not using the feature.

-- 
Ralf


___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex


Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-04 Thread David Kastrup
Ralf Angeli [EMAIL PROTECTED] writes:

 * Stefan Vollmar (2007-07-04) writes:

 That raises the following questions: Is my example especially ugly/ 
 difficult? And why so?

 It's not especially ugly or difficult.

Well, let's say TeX makes it especially ugly and difficult, but that
is not exactly Stefan's fault.

 Judging by the general quality (again: I have only scratched the  
 surface of all the beautiful and powerful features) of a reportedly  
 mature tool like AUCTeX this must be the case - because otherwise  
 people would have that kind of problem all the time.

 It's likely more a case of people not using the feature.

Maybe.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum


___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex


Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-03 Thread David Kastrup
Ralf Angeli [EMAIL PROTECTED] writes:

 Hm, but pasting together random stuff will not be trivial.

Would be the job of the filter routine.  Given TeX's byte-centricity,
it would have to be done even before decoding the byte stream into
characters.

 TeX even adds a blank after the last character of a line.  I'll
 check if working with interspersed occurrences of \s-{0,2} is
 feasible.  But I have my doubts it will be.

Pretty hopeless, I'd guess.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum


___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex


[AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-02 Thread Stefan Vollmar

Dear Ralf,

I have assembled a little collection of TeX-files (emtest.tar.gz,  
attached) that demonstrate the problems I have reported earlier: when  
debugging a multifile document (which now has correct settings for %% 
% TeX-master, etc. at the end of each file), TeX-next-error does  
not show the offending TeX lines corresponding to the log's error  
messages in all cases.


This time, I have included a TeX-submit-bug-report. It appears that  
I can observe the same behaviour of Emacs/Auctex on Linux (attached  
in the bugreport) and the current Aquamax on MacOS:


I provoke two identical errors in two different files of this  
multifile document:


in file vhist_intro.tex:
\rwar{this-is-an-undefined-macro-into}

in file vhist_spec0.tex:
\rwar{this-is-an-undefined-macro-spec0}

only the second one is displayed correctly by TeX-submit-bug-report.

Many thanks in advance,
 Stefan
--
Dr. Stefan Vollmar, Dipl.-Phys.
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213  FAX +49-221-4726-298
Tel.: +49-221-478-5713  Mobile: 0173-5340707
Email: [EMAIL PROTECTED]   http://www.nf.mpg.de
To: [EMAIL PROTECTED]
Subject: 11.84; TeX-next-error does not jump to next error
--text follows this line--

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

Be sure to consult the FAQ section in the manual before submitting
a bug report.  If the bug (or problem) is triggered by a specific
(La)TeX file, you should try to produce a minimal sample file
showing the problem and include it in your report.

Your bug report will be posted to the AUCTeX bug reporting list.


when running latex on vhist_spec0.tex (one file in the attached zip-archive), 
the master file vhist.tex is displayed, a pdf-file get written. Using 
TeX-next-error I expected to Emacs to open the appropriate file and show the 
offending TeX lines, one after the other. However, only the last (provoked) 
error \rwar{this-is-an-undefined-macro-spec0} will be displayed in this 
manner - all other errors are listed (correctly) but not displayed in another 
buffer.


Emacs  : GNU Emacs 21.4.1 (x86_64-redhat-linux-gnu, X toolkit, Xaw3d scroll 
bars)
 of 2007-02-12 on hs20-bc1-6.build.redhat.com
Package: 11.84

current state:
==
(setq
 AUCTeX-date 2007-01-12
 window-system nil
 LaTeX-version 2e
 TeX-style-path '(style auto /usr/share/emacs/site-lisp/auctex/style 
/var/auctex)
 TeX-auto-save t
 TeX-parse-self t
 TeX-master vhist
 TeX-command-list '((TeX %(PDF)%(tex) %`%S%(PDFout)%(mode)%' %t TeX-run-TeX 
nil
 (plain-tex-mode ams-tex-mode texinfo-mode) :help Run 
plain TeX)
(LaTeX %`%l%(mode)%' %t TeX-run-TeX nil (latex-mode 
doctex-mode) :help Run LaTeX)
(Makeinfo makeinfo %t TeX-run-compile nil 
(texinfo-mode) :help
 Run Makeinfo with Info output)
(Makeinfo HTML makeinfo --html %t TeX-run-compile nil 
(texinfo-mode) :help
 Run Makeinfo with HTML output)
(AmSTeX %(PDF)amstex %`%S%(PDFout)%(mode)%' %t 
TeX-run-TeX nil (ams-tex-mode) :help
 Run AMSTeX)
(ConTeXt texexec --once --texutil %(execopts)%t 
TeX-run-TeX nil (context-mode) :help
 Run ConTeXt once)
(ConTeXt Full texexec %(execopts)%t TeX-run-TeX nil 
(context-mode) :help
 Run ConTeXt until completion)
(BibTeX bibtex %s TeX-run-BibTeX nil t :help Run 
BibTeX)
(View dvi2tty -q -w 132 %s TeX-run-command t t :help 
Run Text viewer)
(Print %p TeX-run-command t t :help Print the file)
(Queue %q TeX-run-background nil t :help View the 
printer queue :visible
 TeX-queue-command)
(File %(o?)dvips %d -o %f  TeX-run-command t t :help 
Generate PostScript file)
(Index makeindex %s TeX-run-command nil t :help Create 
index file)
(Check lacheck %s TeX-run-compile nil (latex-mode) :help
 Check LaTeX file for correctness)
(Spell (TeX-ispell-document \\) TeX-run-function nil 
t :help
 Spell-check the document)
(Clean TeX-clean TeX-run-function nil t :help Delete 
generated intermediate files)
(Clean All (TeX-clean t) TeX-run-function nil t :help
 Delete generated intermediate and output files)
(Other  TeX-run-command t t :help Run an arbitrary 
command))
 )


emtest.tar.gz
Description: GNU Zip compressed data




___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex


Re: [AUCTeX] debugging of multifile documents with TeX-next-error (2)

2007-07-02 Thread Ralf Angeli
* Stefan Vollmar (2007-07-02) writes:

 I provoke two identical errors in two different files of this  
 multifile document:

 in file vhist_intro.tex:
 \rwar{this-is-an-undefined-macro-into}

 in file vhist_spec0.tex:
 \rwar{this-is-an-undefined-macro-spec0}

 only the second one is displayed correctly by TeX-submit-bug-report.

If I open vhist_spec0.tex in Emacs, execute `C-c C-c LaTeX RET' and then
jump to the first error with `C-c `', the file vhist_intro.tex will be
opened in the top window with point at the offending macro.  The bottom
window will display the corresponding help text of the error.  If I
execute `C-c `' again, the analogous action happens for vhist_spec0.tex.
So in my case this works flawlessly.

If you had included the output buffer contents as requested, I probably
could have found out more.

-- 
Ralf


___
auctex mailing list
auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/auctex