From: Hans Hagen <pragma@wxs.nl>
Subject: Re: texexec is very coy
Date: Wed, 19 Apr 2006 09:29:54 +0200 [thread overview]
Message-ID: <4445E6F2.3050405@wxs.nl> (raw)
In-Reply-To: <E1FVyrB-0000CR-49@approximate.corpus.cam.ac.uk>
Sanjoy Mahajan wrote:
> When texexec doesn't find a program or a file, it doesn't complain
> loudly. In this output from a recent run
>
> extra program : dvipos z
>
> total run time : 3 seconds
>
> texexec went looking for 'dvipos'. I didn't suspect any problem since I
> didn't know that it wasn't installed (and hadn't heard of it until a few
> hours ago). An error message like this would be useful::
>
> extra program : dvipos z
> ERROR: Could not run 'dvipos'
> total run time : 3 seconds
>
> Perhaps at the end of the run repeat all those error msgs (otherwise
> they gets buried in all the output).
>
> A similar message would be useful when the tex file itself doesn't exist:
>
> $ texexec nosuchfile.tex
>
> TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
>
> fixing engine variable : pdfetex
>
> total run time : 1 seconds
>
> Eventually I learnt that a run time of 1 second meant I'd mistyped the
> file name, but a message would be useful (and more helpful than
> prompting for the correct filename: I like Unix programs to not ask
> questions).
>
i'm not going to spend much more time on oldtexexec; i've added a message to newtexexec:
TeXExec | processing document 'x'
TeXExec | no ctx file found
TeXExec | nothing to process
TeXExec | runtime: 0.01
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
prev parent reply other threads:[~2006-04-19 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 22:39 Sanjoy Mahajan
2006-04-19 7:29 ` Hans Hagen [this message]
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=4445E6F2.3050405@wxs.nl \
--to=pragma@wxs.nl \
--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).