From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Subject: Re: A proposal for texexec
Date: 22 Jun 2000 23:13:05 +0200 [thread overview]
Message-ID: <87u2elh126.fsf@localhost.localnet> (raw)
In-Reply-To: Hans Hagen's message of "Tue, 20 Jun 2000 09:21:50 +0200"
Hans Hagen <pragma@wxs.nl> writes:
> The solution would be to use a temp file for processing. However, the
> problem is that in that case the jobname changes as well as all auxiliary
> files. This is not a problem in a stand alone or final run, but not that
> handy when debugging files, since in some aspects the filename is
> important. So, it's not that trivial. I can write a complement to --result
> (--temp) but I wonder if it wouldn't introduce other problems.
Hmm. It would be feasible if the name for temp file remained the
same (suffix). Then renaming only the resulting (pdf/ps/dvi) file
would do the trick.
--
hundred-and-one symptoms of being an internet addict:
186. You overstay in the office so you can have more time surfing the net.
Suavek Zak / PGP: finger://zaks@prioris.mini.pw.edu.pl
next prev parent reply other threads:[~2000-06-22 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-18 15:49 Slawek Zak
2000-06-14 10:40 ` Berend de Boer
2000-06-19 17:31 ` Slawek Zak
2000-06-20 7:21 ` Hans Hagen
2000-06-22 21:13 ` Slawek Zak [this message]
2000-06-18 21:03 ` Hans Hagen
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=87u2elh126.fsf@localhost.localnet \
--to=zaks@prioris.mini.pw.edu.pl \
/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).