From: Nate Eldredge <neldredge@math.ucsd.edu>
To: Ralf Angeli <angeli@caeruleus.net>
Cc: bug-gnu-emacs@gnu.org, 376@emacsbugs.donarmstrong.com
Subject: bug#376: latex error message starts dired
Date: Sun, 8 Jun 2008 01:33:32 -0700 (PDT) [thread overview]
Message-ID: <Pine.GSO.4.64.0806080132010.20326@zeno.ucsd.edu> (raw)
In-Reply-To: <87ve0ktkth.fsf@photon.caeruleus.net>
On Sun, 8 Jun 2008, Ralf Angeli wrote:
> * Nate Eldredge (2008-06-08) writes:
>
>> Here is the output of latex, as it appears in the *tex-shell* buffer.
>
>> Runaway argument?
>> g(\polar , s) &= \Re \phi (se^{i\polar })\frac {1}{4\pi }s \psi (i(\pi \ETC.
>> ! Paragraph ended before \align was complete.
>
> The parser finds this error and subsequently tries to determine the file
> name. In course of that it checks the "(\pi" construct with point right
> before the backslash. In this case the form
> (file-readable-p (thing-at-point 'filename))
> returns t and the file name is set to an empty string. (This is what
> `(thing-at-point 'filename)' returns.)
>
> I'm not sure if this is a problem with `thing-at-point' or
> `file-readable-p'.
>
> As a workaround you could enable file:line:error messages for latex.
Ah, thanks for the suggestion. I did not know about that feature. That
solves the problem for me.
Thanks for investigating this bug.
--
Nate Eldredge
neldredge@math.ucsd.edu
next prev parent reply other threads:[~2008-06-08 8:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y73pkdmw.fsf@stupidchicken.com>
2008-06-08 3:41 ` bug#376: latex error message starts dired Nate Eldredge
2008-06-08 8:03 ` Ralf Angeli
2008-06-08 8:33 ` Nate Eldredge [this message]
2008-07-25 18:50 ` bug#376: marked as done (latex error message starts dired) Emacs bug Tracking System
2008-07-25 17:35 bug#376: latex error message starts dired Chong Yidong
2008-07-25 17:50 ` Ralf Angeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.64.0806080132010.20326@zeno.ucsd.edu \
--to=neldredge@math.ucsd.edu \
--cc=376@emacsbugs.donarmstrong.com \
--cc=angeli@caeruleus.net \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.