ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Slawek Zak <zaks@prioris.mini.pw.edu.pl>
Subject: A proposal for texexec
Date: 18 Jun 2000 17:49:02 +0200	[thread overview]
Message-ID: <87bt0z0z2p.fsf@localhost.localnet> (raw)

I think that it would be very useful if the file produced by TeX
invoked from texexec was placed under other name than the final
(.ps/.pdf) file and renamed when the compilation is over (=atomic
update).

It is difficult to work with pdf/ps viewers "watching" modification
time of the resulting file as a sign for redisplay (say gv); as they
try to display the incomplete file and popup a window with error
messages.

I think that it would be trivial to implement (there already is
--result option for texexec).
--
In a world without walls and borders, who needs windows and gates?
Suavek Zak / PGP: finger://zaks@prioris.mini.pw.edu.pl


             reply	other threads:[~2000-06-18 15:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-18 15:49 Slawek Zak [this message]
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
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=87bt0z0z2p.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).