From: Philipp Reichmuth <reichmuth@web.de>
Subject: Re: Parsing texexec output
Date: Tue, 07 Nov 2006 00:23:39 +0100 [thread overview]
Message-ID: <eiog5q$ac1$1@sea.gmane.org> (raw)
In-Reply-To: <Pine.WNT.4.63.0611061807260.3756@nqvgln>
Aditya Mahajan schrieb:
>> 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?
>
> texexec --nonstopmode
Does the job, thanks. AucTeX assumes
--passon="-interaction=nonstopmode", which doesn't work.
> Another option, sometimes used by vim-latex suite is to add 'type
> filename.log' or 'cat filename.log' at the end the command. The parser
> will not know the difference.
I had thought of that, but it spoils the return code, at least here on
Windows.
Philipp
next prev parent reply other threads:[~2006-11-06 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 22:48 Philipp Reichmuth
2006-11-06 23:14 ` Aditya Mahajan
2006-11-06 23:23 ` Philipp Reichmuth [this message]
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='eiog5q$ac1$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).