From: "Berend de Boer" <berend@pobox.com>
Subject: RE: A proposal for texexec
Date: Wed, 14 Jun 2000 12:40:40 +0200 [thread overview]
Message-ID: <00fc01bfd5ec$fc800630$0321a8c0@bmach.nederware.nl> (raw)
In-Reply-To: <87bt0z0z2p.fsf@localhost.localnet>
> I think that it would be trivial to implement (there already is
> --result option for texexec).
Or fix the viewers :-) They should attempt to open the file for exclusive
use or with deny write or something like that: if not possible the file is
not yet ready. These viewers are too greedy.
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2000-06-14 10:40 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 [this message]
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='00fc01bfd5ec$fc800630$0321a8c0@bmach.nederware.nl' \
--to=berend@pobox.com \
/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).