ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Reichmuth <reichmuth@web.de>
Subject: Parsing texexec output
Date: Mon, 06 Nov 2006 23:48:54 +0100	[thread overview]
Message-ID: <eioe4l$42j$1@sea.gmane.org> (raw)

Hi,

I was fixing a bug in my AucTeX and found that at present it is 
difficult to parse the output from texexec.  Basically Emacs runs 
texexec in a buffer in --batchmode, then tries to parse the output 
whether an error occurred and where.  Unfortunately with texexec I don't 
get any error messages (besides the return code), so if something goes 
wrong, the user only knows that something isn't right, but not what it 
is.  (It also doesn't print page numbers, either.)  In comparison, LaTeX 
when run in \nonstopmode prints the error message normally and continues 
to process the file; that makes it easy to parse it, jump to the line 
where the error was detected and even present the user with an 
explanation of the error message.

In order to get similar features with ConTeXt, it would be nice if 
texexec could be made to be a little bit more verbose in its --batchmode 
output.  Is there a way to do this currently?

Philipp

             reply	other threads:[~2006-11-06 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-06 22:48 Philipp Reichmuth [this message]
2006-11-06 23:14 ` Aditya Mahajan
2006-11-06 23:23   ` Philipp Reichmuth
2006-11-06 23:40     ` Hans Hagen
2006-11-07  5:57     ` Sanjoy Mahajan
2006-11-07  7:55       ` Philipp Reichmuth
2006-11-07  7:59       ` Taco Hoekwater
2006-11-11 22:27     ` Leo
2006-11-13 20:13       ` Philipp Reichmuth
2006-11-14 16:28         ` Leo
2006-11-23 16:18           ` Patrick Gundlach

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='eioe4l$42j$1@sea.gmane.org' \
    --to=reichmuth@web.de \
    --cc=ntg-context@ntg.nl \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).