From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Closing PDF file at each run
Date: Tue, 28 Feb 2006 09:01:21 +0100 [thread overview]
Message-ID: <44040351.1050609@elvenkind.com> (raw)
In-Reply-To: <Pine.SOL.4.21.0602280114050.13001-100000@sun15.eng.uwo.ca>
Hooman Javidnia wrote:
> but still the PDF is not refreshed for the second run. I am using Acrobat
> 7. I read in WinEdt's mailing list that Adobe Acrobat has changed its
> caption from version 6 onwards. Could this be a problem related to the
> versions of Acrobat?
I wouldn't think so. Perhaps texexec cannot find pdfopen?
(I am out of my league now, not using windows myself)
Cheers,
Taco
next prev parent reply other threads:[~2006-02-28 8:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 7:22 Hooman Javidnia
2006-02-27 9:48 ` Taco Hoekwater
2006-02-27 10:26 ` Johan Sandblom
2006-02-27 10:58 ` Taco Hoekwater
2006-02-28 6:29 ` Hooman Javidnia
2006-02-28 8:01 ` Taco Hoekwater [this message]
2006-02-28 9:10 ` Hans Hagen
2006-03-01 5:19 ` Hooman Javidnia
2006-02-27 12:02 ` Mojca Miklavec
[not found] <B3C24EA955FF0C4EA14658997CD3E25E01B5C452@CAHIER.gst.uqam.ca>
2006-03-01 3:51 ` FabriceL.
2006-03-01 9: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=44040351.1050609@elvenkind.com \
--to=taco@elvenkind.com \
--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).