From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: A proposal for texexec
Date: Tue, 20 Jun 2000 09:21:50 +0200 [thread overview]
Message-ID: <3.0.6.32.20000620092150.018e57a0@pop.wxs.nl> (raw)
In-Reply-To: <87hfap37cq.fsf@localhost.localnet>
At 07:31 PM 6/19/00 +0200, Slawek Zak wrote:
>"Berend de Boer" <berend@pobox.com> writes:
>
>> > 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.
>
>Well, this is a desired behaviour. When the file is recompiled (newer
>than the it was) they try to reopen and redisplay it. Good thing. It
>wouldn't break if the refresh happened only when you make the viewer
>redisplay it's window :)
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.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.nl
-------------------------------------------------------------------------
next prev parent reply other threads:[~2000-06-20 7:21 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 [this message]
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=3.0.6.32.20000620092150.018e57a0@pop.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).