From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Subject: Re: What a pain!
Date: Fri, 04 Jun 1999 09:20:24 +0000 (GMT) [thread overview]
Message-ID: <14167.39512.117099.314808@gargle.gargle.HOWL> (raw)
In-Reply-To: <3.0.5.32.19990603182423.00a5da10@mail.northcoast.com>
>>>>> "David" == David Arnold <darnold@northcoast.com> writes:
David> All, I have Acrobat Reader 4.0. Everytime I compile
David> junk.tex to junk.pdf, I have to have the file junk.pdf
David> closed in AR4. What a pain.
David> Is there anyway to leave junk.pdf open in AR4, compile
David> junk.tex to junk.pdf, then have the result displayed in
David> AR4?
No. All versions of Reader under Windows behave this way. Linux
version is slightly better: there is no lock on the pdf file, so that
compiling works, but you still need to close and re-open to get at the
new file.
Taco
next prev parent reply other threads:[~1999-06-04 9:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-04 1:24 David Arnold
1999-06-04 6:53 ` Hans Hagen
1999-06-04 10:44 ` Tobias Burnus
1999-06-04 9:20 ` Taco Hoekwater [this message]
1999-06-04 7:23 ` Hans Hagen
1999-06-04 10:44 ` Tobias Burnus
1999-06-04 9:28 ` Taco Hoekwater
1999-06-04 9:31 ` Taco Hoekwater
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=14167.39512.117099.314808@gargle.gargle.HOWL \
--to=taco.hoekwater@wkap.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).