ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "FabriceL." <larribe.fabrice@uqam.ca>
Subject: Re: Closing PDF file at each run
Date: Tue, 28 Feb 2006 22:51:27 -0500	[thread overview]
Message-ID: <44051A3F.4010400@uqam.ca> (raw)
In-Reply-To: <B3C24EA955FF0C4EA14658997CD3E25E01B5C452@CAHIER.gst.uqam.ca>


Hooman Javidnia a écrit :
>
> Hi,
>
> When compiling a file in SciTE using F7, if the file, is already open in
> Adobe Acrobat, the compilation stops and asks for a new file name to write
> the PDF file to. I think the normal behavior would be to automatically
> close the current instance of the file in Acrobat and compile it again.
>
> Is there something wrong with my installation, or this is a bug?
> Regards, -- Hooman
>
Hi. This is interesting, since I have the same problem with WinEdt and 
Acrobat (on Windows). I had notice
that is there is not input file in my ConTeXt file, then, when I compile 
by WinEdt interface,
the pdf file is closed with no problem. If I use an "\input file.tex" 
command in the ConTeXt file,
then one ask me a file name for the pdf, since the file can not be 
closed automatically. I had
consult WinEdt mailing  list too, and no solution there. I have no 
solution, but from the symtom
I describe, I suspect this is a ConTeXt thing...

Fabrice.

       reply	other threads:[~2006-03-01  3:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B3C24EA955FF0C4EA14658997CD3E25E01B5C452@CAHIER.gst.uqam.ca>
2006-03-01  3:51 ` FabriceL. [this message]
2006-03-01  9:03   ` Hans Hagen
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
2006-02-28  9:10         ` Hans Hagen
2006-03-01  5:19           ` Hooman Javidnia
2006-02-27 12:02 ` Mojca Miklavec

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=44051A3F.4010400@uqam.ca \
    --to=larribe.fabrice@uqam.ca \
    --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).