Preview-latex(Auctex) problem
senator
I recently downloaded the pre-compiled Emacs+Auctex bundle for Windows
from ftp://alpha.gnu.org/gnu/auctex/emacs+auctex-w32-2006-01-29.zip
(from this page:
http://www.gnu.org/software/auctex/download-for-windows.html). After
getting a few path errors, I found out that I had to configure the
paths to Latex, dvips etc manually. The manuals don't seem to have any
information on this (not for preconfigured packages anyway).
% ------------ Settings -----------------
My settings are: (I used M-x customize-group Auctex and looked for
these, presumably M-x set-variable works too)
Tex Print Command -> o:\MIKTEX\miktex\bin\dvips %d
Tex Command -> o:\MIKTEX\miktex\bin\tex.exe
Latex Command -> o:\MIKTEX\miktex\bin\latex.exe
Preview Gs Command -> c:\gs\gs8.50\bin\GSWIN32C.EXE
Software versions:
This is dvips(k) 5.94a Copyright 2003 Radical Eye Software
(www.radicaleye.com)
Usage: dvips [OPTION]... FILENAME[.dvi]
O:\MiKTeX\miktex\bin>latex
This is e-TeX, Version 3.141592-2.2 (MiKTeX 2.4)
O:\MiKTeX\miktex\bin>tex
This is TeX, Version 3.141592 (MiKTeX 2.4)
C:\gs\gs8.50\bin>gswin32c
GPL Ghostscript 8.50 (2005-12-31)
Copyright (C) 2005 artofcode LLC, Benicia, CA. All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
GNU Emacs 22.0.50.1 (i386-mingw-nt5.1.2600)
of 2006-01-29 on NEUTRINO
% ------------ Settings -----------------
Now, Auctex itself seems to work fine (eg \chapter{My chapter} shows up
in larger font, "TeX" icon appears on toolbar, the "LaTeX" and
"Preview" menu options both appear in the menu bar). The command itself
seems to run (generated a dvi file, looked alright to me).
Preview-latex doesn't quite work yet. For example, within the provided
sample file circ.tex, placing point/cursor within a \begin{equation}
... \end{equation} block and calling "preview-environment" or
"preview-at-point" seems to set things running. I immediately see the
"Man at work" road-sign, but after a while, when I expect to the the
image of the equations, I get an error (no-entry) sign instead.
Right clicking (no binding to keyboard?) on the error sign -> View
error gives:
"c:\gs\gs8.50\bin\GSWIN32C.EXE"
"-dOutputFile=(_region_.prv/tmp1024Vs8/pr1-1.png)" "-q" "-dSAFER"
"-dNOPAUSE" "-DNOPLATFONTS" "-dPrinted" "-dTextAlphaBits=4"
"-dGraphicsAlphaBits=4" "-sDEVICE=png16m" "-r99.568x106.206"
GS>{DELAYSAFER{.setsafe}if}stopped pop/.preview-BP
currentpagedevice/BeginPage get dup null eq {pop{pop}bind}if
def<</BeginPage{currentpagedevice/PageSize get dup 0 get 1 ne exch 1
get 1 ne or{.preview-BP }{pop}ifelse}bind/PageSize[1
1]>>setpagedevice/preview-do{[count 3 roll save]3 1 roll dup length 0
eq{pop}{{setpagedevice}stopped{handleerror quit}if}ifelse systemdict
/.runandhide known{{.runandhide}}if stopped{handleerror quit}if count 1
gt{pop/exec errordict/stackoverflow get exec}if aload pop restore}bind
def (_region_.prv/tmp1024Vs8/preview.ps)(r)file dup dup 0
setfileposition 19524()/SubFileDecode filter cvx exec dup dup 19524
setfileposition 286()/SubFileDecode filter cvx<</PageSize[240.123
26.7055]/PageOffset[71.5 714.176[1 1 dtransform exch]{0 ge{neg}if
exch}forall]>>preview-do
Error: /undefined in /bop-hook
Operand stack:
--nostringval-- bop-hook
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
%loop_continue 2 3 %oparray_pop --nostringval--
--nostringval-- false 1 %stopped_push .runexec2
--nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
--nostringval--
Dictionary stack:
--dict:1125/1686(ro)(G)-- --dict:0/20(G)-- --dict:73/200(L)--
--dict:96/300(L)-- --dict:17/200(L)-- --dict:73/200(L)--
So what could be happening? What other information should I provide for
anyone to help figure this out? Is it some kinda version
incompatibility in the dvips tool? What versions for tex,latex, and
dvips are required (they weren't specified)?
Additional information:Had I tried to generate previews for inlined
equations ($1+1=2$), the process will never stop ("man at work" sign is
up forever, or is it just a long time), so I sometimes get this prompt:
"Process `Preview-Ghostscript' for document `_region_' running, kill
it? (yes or no)".
Finally, I also found the following broken link:
>From http://www.gnu.org/software/auctex/manual/html_node/index.html,
middle of page: install (2 identical links) to:
http://www.gnu.org/software/auctex/manual/preview-latex/Installation.html#Installation
I think that's it, I've been reading through the manuals and Googled
the newsgroups, so I don't think I've missed anything (if I have,
pointers would be very much appreciated). Cheers,
David Kastrup
> I recently downloaded the pre-compiled Emacs+Auctex bundle for Windows
> from ftp://alpha.gnu.org/gnu/auctex/emacs+auctex-w32-2006-01-29.zip
> (from this page:
> http://www.gnu.org/software/auctex/download-for-windows.html). After
> getting a few path errors, I found out that I had to configure the
> paths to Latex, dvips etc manually. The manuals don't seem to have any
> information on this (not for preconfigured packages anyway).
You need to put the stuff in your PATH variable. There is some
menu/system settings stuff in Windows to do that, but I always forget
what it is, since I don't use Windows.
> % ------------ Settings -----------------
> My settings are: (I used M-x customize-group Auctex and looked for
> these, presumably M-x set-variable works too)
> Tex Print Command -> o:\MIKTEX\miktex\bin\dvips %d
> Tex Command -> o:\MIKTEX\miktex\bin\tex.exe
> Latex Command -> o:\MIKTEX\miktex\bin\latex.exe
> Preview Gs Command -> c:\gs\gs8.50\bin\GSWIN32C.EXE
No, just adjust your PATH by adding the directories of the binaries.
Everything else will be troublesome.
Wrong version of preview.sty or broken paths.
> What other information should I provide for anyone to help figure
> this out?
The bug reporting instructions? After you tried running
preview-latex, use
M-x preview-report-bug RET
or the respective menu entry.
This will fill in most of the required information. If you mail
system is not working inside of Emacs, cut&paste the created mail into
your mailer instead of sending it.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
UKTUG FAQ: <URL:http://www.tex.ac.uk/cgi-bin/texfaq2html>
Lars Madsen
> "senator" <senator...@gmail.com> writes:
>
>> I recently downloaded the pre-compiled Emacs+Auctex bundle for Windows
>> from ftp://alpha.gnu.org/gnu/auctex/emacs+auctex-w32-2006-01-29.zip
>> (from this page:
>> http://www.gnu.org/software/auctex/download-for-windows.html). After
>> getting a few path errors, I found out that I had to configure the
>> paths to Latex, dvips etc manually. The manuals don't seem to have any
>> information on this (not for preconfigured packages anyway).
>
> You need to put the stuff in your PATH variable. There is some
> menu/system settings stuff in Windows to do that, but I always forget
> what it is, since I don't use Windows.
>
Start > Control Panel > Advanced Settings > Environment Variables
If I'm not mistaken.
/daleif
senator
case anyone needs it:
The path is now managed by Windows 2000 / Windows XP and not the
autoexec.bat or autoexec.nt files. To change the system environment
variables, follow the below steps.
1. From the desktop, right click My Computer and click properties.
2. In the System Properties window, click on the Advanced tab.
3. In the Advanced section, click the Environment Variables button.
4. Finally, in the Environment Variables window, highlight the path
variable in the Systems Variable section and click edit. Add or modify
the path lines with the paths you wish the computer to access. Each
different directory is separated with a semicolon as shown below.
C:\Program Files;C:\Winnt;C:\Winnt\System32
%--------------------------------------------------------------------
Well, I set the miktek path to the right places (this time to my c
drive (had another copy on o drive before). It still gives the same
sort of error.
Because the M-x preview-report-bug generated output is so big, I have
pasted it here instead: http://paste.lisp.org/display/16535
I might have stuffed up some formatting in this paste with
auto-fill-mode. The annotation for this paste also has the additional
output from right clicking on the error signs.
Anymore ideas on what I should do?
Ulrike Fischer
>> After
>> getting a few path errors, I found out that I had to configure the
>> paths to Latex, dvips etc manually.
> You need to put the stuff in your PATH variable.
I think it would be a good idea to mention the path problem explicitly
in the installation instructions: Winedt users don't need to set the
path as winedt gets everything from the registry, so windows/winedt
users (which nowadays often don't know about PATH) can be a bit
confused if a working TeX-installation with winedt doesn't work with
emacs/auctex.
--
Ulrike Fischer
e-mail: zusätzlich meinen Vornamen vor dem @ einfügen.
e-mail: add my first name between the news and the @.
David Kastrup
> Wow, thanks for the prompt reply. I found this (pasted here just in
> case anyone needs it:
>
> Because the M-x preview-report-bug generated output is so big, I have
> pasted it here instead: http://paste.lisp.org/display/16535
>
> I might have stuffed up some formatting in this paste with
> auto-fill-mode. The annotation for this paste also has the additional
> output from right clicking on the error signs.
>
> Anymore ideas on what I should do?
As I already said: for some reason you are using an utterly outdated
version of preview.sty (about 4 years old, from 0.7.2b).
Also as I said: you should mail your report to the bug-auctex list,
like the bug reporting command suggests.
This bug is related with how the precompiled AUCTeX/Emacs are set up,
and I am not a user of Windows. If you want to reach the appropriate
developer instead of arbitrary bystanders, use the bug reporting
list.
David Kastrup
> David Kastrup <d...@gnu.org> schrieb:
>
>>> After
>>> getting a few path errors, I found out that I had to configure the
>>> paths to Latex, dvips etc manually.
>
>> You need to put the stuff in your PATH variable.
>
> I think it would be a good idea to mention the path problem
> explicitly in the installation instructions: Winedt users don't need
> to set the path as winedt gets everything from the registry, so
> windows/winedt users (which nowadays often don't know about PATH)
> can be a bit confused if a working TeX-installation with winedt
> doesn't work with emacs/auctex.
Ralf? I mostly did not put anything in the instructions because I
actually have no clue or Windows.
And we probably should mention the precompiled stuff somewhere, too,
and how to deal with it.
senator
> > Anymore ideas on what I should do?
>
> As I already said: for some reason you are using an utterly outdated
> version of preview.sty (about 4 years old, from 0.7.2b).
> Also as I said: you should mail your report to the bug-auctex list,
> like the bug reporting command suggests.
What I was going to say:
Ok, I've mailed that off as a bug report (it wasn't clear to me before
if it was a bug yet). I don't think it's gonna get through though,
cause it has been bounced awaiting moderator approval... I will try to
join the mailing list, and am currently looking through the archives.
There seem to be a lot going on there.
Update:
>From the archives, I was led to the CTAN version of preview-latex
(similar to this one:
http://www.ctan.org/tex-archive/macros/latex/contrib/preview/). It is
exactly the same as the one distributed with the prepackaged windows
distribution (so it had the right version after all). I found out that
there was actually another copy of "preview" with my Miktex
distribution (the outdated one), so that was why. I replaced the
contents in path\to\miktex\preview with the updated version, and it
works now!!! I'm so happy (that only took 1 week).
That's the catch to watch out for - even if one was not using
Emacs+Auctex+Preview-latex before, one could have outdated versions of
files lying around pre-bundled with the Miktex/Latex distribution.
So uh, I need to cancel the bug report I sent (too late for that one).
It's not a bug afterall. Should I send another bug report to cancel the
previous one? Many thanks for all that help. Have a nice one.
Ralf Angeli
> Ulrike Fischer <ne...@nililand.de> writes:
>
>> David Kastrup <d...@gnu.org> schrieb:
>>
>>> You need to put the stuff in your PATH variable.
>>
>> I think it would be a good idea to mention the path problem
>> explicitly in the installation instructions: Winedt users don't need
>> to set the path as winedt gets everything from the registry, so
>> windows/winedt users (which nowadays often don't know about PATH)
>> can be a bit confused if a working TeX-installation with winedt
>> doesn't work with emacs/auctex.
What exactly does WinEdt get from the registry? AFAICS there is no
path-related information set by MikTeX in the registry except for PATH
itself which gets exported to the environment. So actually AUCTeX
should work out-of-the-box with MikTeX unless you broke your MikTeX
installation e.g. by moving stuff around.
> Ralf?
Just as a note, I don't follow ctt currently.
> I mostly did not put anything in the instructions because I
> actually have no clue or Windows.
>
> And we probably should mention the precompiled stuff somewhere, too,
> and how to deal with it.
Basically it boils down to "Make sure that the executables AUCTeX
needs are in your system path." which we could put more prominently in
the installation instructions or the FAQ.
--
Ralf
Ulrike Fischer
> What exactly does WinEdt get from the registry? AFAICS there is no
> path-related information set by MikTeX in the registry except for PATH
> itself which gets exported to the environment. So actually AUCTeX
> should work out-of-the-box with MikTeX unless you broke your MikTeX
> installation e.g. by moving stuff around.
I don't know exactly, but you can use LaTeX etc from winedt without
setting PATH (I'm sure because I had to set the pathes on a WinXP with
working Winedt/MiKTeX before I could try emacs).
On my (old installation) here MiKTeX stores the pathes to the
texmf-trees so winedt perhaps makes a good guess about the location of
the binaries.
Ghostcript stores the pathes to the binaries in the registry, so this
is easy for winedt to get.
David Kastrup
> Ok, I've mailed that off as a bug report (it wasn't clear to me
> before if it was a bug yet). I don't think it's gonna get through
> though, cause it has been bounced awaiting moderator approval...
I approved it since then.
> Update:
>>From the archives, I was led to the CTAN version of preview-latex
> (similar to this one:
> http://www.ctan.org/tex-archive/macros/latex/contrib/preview/). It is
> exactly the same as the one distributed with the prepackaged windows
> distribution (so it had the right version after all). I found out that
> there was actually another copy of "preview" with my Miktex
> distribution (the outdated one), so that was why. I replaced the
> contents in path\to\miktex\preview with the updated version, and it
> works now!!! I'm so happy (that only took 1 week).
The normal setup should take care that preview-latex's own variant of
preview.sty is found first. If it doesn't, that's a bug.
> That's the catch to watch out for - even if one was not using
> Emacs+Auctex+Preview-latex before, one could have outdated versions
> of files lying around pre-bundled with the Miktex/Latex
> distribution.
They should not make a difference.
> So uh, I need to cancel the bug report I sent (too late for that
> one). It's not a bug afterall. Should I send another bug report to
> cancel the previous one? Many thanks for all that help. Have a nice
> one.
It is a bug. I'll get back to you on the list, and hopefully we'll be
able to figure out why preview-latex's own version is not used here.
Ralf Angeli
> Ralf Angeli <dev....@iwi.uni-sb.de> schrieb:
>
>> What exactly does WinEdt get from the registry? AFAICS there is no
>> path-related information set by MikTeX in the registry except for PATH
>> itself which gets exported to the environment. So actually AUCTeX
>> should work out-of-the-box with MikTeX unless you broke your MikTeX
>> installation e.g. by moving stuff around.
>
> I don't know exactly, but you can use LaTeX etc from winedt without
> setting PATH (I'm sure because I had to set the pathes on a WinXP with
> working Winedt/MiKTeX before I could try emacs).
I wonder why MikTeX did not adapt PATH in your case.
> On my (old installation) here MiKTeX stores the pathes to the
> texmf-trees so winedt perhaps makes a good guess about the location of
> the binaries.
If WinEdt was free software we could easily find out.
> Ghostcript stores the pathes to the binaries in the registry, so this
> is easy for winedt to get.
Hm, I could not find a Lisp interface for accessing the registry in
Emacs.
--
Ralf
Brian Elmegaard
> I wonder why MikTeX did not adapt PATH in your case.
It sets several registry values, e.g.,
HKLM\SOFTWARE\MiK\MiKTeX\CurrentVersion\MiKTeX\TeXMF Root Directories
and it is registered under insatllaed programs.
> Hm, I could not find a Lisp interface for accessing the registry in
> Emacs.
It is quite peculiar to me that the installation of emacsw32
http://www.emacswiki.org/cgi-bin/wiki/EmacsW32 sets a registry entry
for the emacs itself, but does not add to PATH.
--
Brian (remove the sport for mail)
http://www.et.web.mek.dtu.dk/Staff/be/be.html
http://www.rugbyklubben-speed.dk
Ralf Angeli
> Ralf Angeli <dev....@iwi.uni-sb.de> writes:
>
>> I wonder why MikTeX did not adapt PATH in your case.
>
> It sets several registry values, e.g.,
> HKLM\SOFTWARE\MiK\MiKTeX\CurrentVersion\MiKTeX\TeXMF Root Directories
> and it is registered under insatllaed programs.
How are your examples related to accessing executables installed with
MikTeX? Regarding PATH the relevant registry entry is in
HKLM\System\CurrentControlSet\Control\Session Manager\Environment or
the respective per-user key. Those are set by MikTeX in
`RegisterPathNT', see
<URL:http://cvs.miktex.org/viewcvs.py/miktex/miktex/Wizards/Setup/Setup.cpp?view=markup>.
>> Hm, I could not find a Lisp interface for accessing the registry in
>> Emacs.
>
> It is quite peculiar to me that the installation of emacsw32
> http://www.emacswiki.org/cgi-bin/wiki/EmacsW32 sets a registry entry
> for the emacs itself, but does not add to PATH.
Probably because there are no other programs relying on it. It is
quite common that a program installed on Windows is only started via
an entry in the Start menu or a file type association without having
to be present in PATH.
--
Ralf
Ulrike Fischer
>> I don't know exactly, but you can use LaTeX etc from winedt without
>> setting PATH (I'm sure because I had to set the pathes on a WinXP with
>> working Winedt/MiKTeX before I could try emacs).
>
> I wonder why MikTeX did not adapt PATH in your case.
I don't know. I don't think that MiKTeX has set PATH in any
installation I have done over the years: I always had to change
autoexec.bat or something similar. But I couldn't find something in the
manual about the path, so I wonder if my recollection is correct.
>
>> On my (old installation) here MiKTeX stores the pathes to the
>> texmf-trees so winedt perhaps makes a good guess about the location of
>> the binaries.
>
> If WinEdt was free software we could easily find out.
I looked a bit in the startup macros Winedt use: It reads the registry
(I guess with some standard windows method or tool like reg.exe) and
searchs for miktex (there are also scripts for fptex and Yandy) and
gets the texmf- path (if there isn't anything in the registry it tries
some common pathes to find a tex). Then it look if there is a tex in
../texmf/miktex/bin and if it works it adds the path to PATH.
>> Ghostcript stores the pathes to the binaries in the registry, so this
>> is easy for winedt to get.
>
> Hm, I could not find a Lisp interface for accessing the registry in
> Emacs.
I had only suggested that you mention the problem with a perhaps wrong
PATH variable in the installation instructions, at the end it isn't
much work to add something to PATH - you only need to know that you
should do it.
But if you want to do more: I did found an interface mentioned:
http://lists.gnu.org/archive/html/emacs-devel/2004-10/msg00536.html
Sadly the mentioned page is down, but one can find an old version on
archive.org:
http://web.archive.org/web/20041021225526/www.gnusoftware.com/Emacs/Registr
y/
But I don't know if it is necessary to read the registy. At the
installation auctex did ask me for the path and make/configure etc did
seem to check the binaries. So I would say it should be easy to store
the values in emacs and offer a possibility to use this values to
change the path before a LaTeX run.
Ralf Angeli
> Ralf Angeli <dev....@iwi.uni-sb.de> schrieb:
>
>> I wonder why MikTeX did not adapt PATH in your case.
>
> I don't know. I don't think that MiKTeX has set PATH in any
> installation I have done over the years: I always had to change
> autoexec.bat or something similar. But I couldn't find something in the
> manual about the path, so I wonder if my recollection is correct.
Maybe former versions didn't set PATH. I'm pretty sure that current
versions do it because of what I saw in the source code. Additionally
I asked a colleague who uses MikTeX with WinEdt and who told me that
he didn't change PATH manually to show me the value of PATH on his
computer and it included an entry for MikTeX's bin directory. Also,
MikTeX's installation instructions suggest to run latex on a file from
the Windows prompt which is likely to fail if latex is not in PATH.
> I looked a bit in the startup macros Winedt use: It reads the registry
> (I guess with some standard windows method or tool like reg.exe) and
> searchs for miktex (there are also scripts for fptex and Yandy) and
> gets the texmf- path (if there isn't anything in the registry it tries
> some common pathes to find a tex). Then it look if there is a tex in
> ../texmf/miktex/bin and if it works it adds the path to PATH.
Thanks for this information. WinEdt jumping through all those hoops
could indicate that MikTeX didn't set PATH in former versions. Maybe
the OP had or still has such a version.
> I had only suggested that you mention the problem with a perhaps wrong
> PATH variable in the installation instructions, at the end it isn't
> much work to add something to PATH - you only need to know that you
> should do it.
I'll add that piece of information.
> But if you want to do more: I did found an interface mentioned:
Thanks.
> But I don't know if it is necessary to read the registy.
For MikTeX it should not be necessary. For detecting Ghostscript it
could be useful.
> At the
> installation auctex did ask me for the path and make/configure etc did
> seem to check the binaries.
There is no configuration if you download the Emacs/AUCTeX bundle.
You simply unpack it at the desired location and can start using it
... if PATH is set up correctly. (c;
> So I would say it should be easy to store
> the values in emacs and offer a possibility to use this values to
> change the path before a LaTeX run.
If the configuration found all the executables, Emacs should do so as
well.
--
Ralf
Brian Elmegaard
> How are your examples related to accessing executables installed with
> MikTeX?
My mistake. I misunderstood your post and thought it didn't set PATH.
> Probably because there are no other programs relying on it.
There could be several uses for it, e.g. for using emacs as external
editor.
Brian Elmegaard
Ulrike Fischer
>>> I wonder why MikTeX did not adapt PATH in your case.
>>
>> I don't know. I don't think that MiKTeX has set PATH in any
>> installation I have done over the years: I always had to change
>> autoexec.bat or something similar. But I couldn't find something in the
>> manual about the path, so I wonder if my recollection is correct.
>
> Maybe former versions didn't set PATH. I'm pretty sure that current
> versions do it because of what I saw in the source code. Additionally
> I asked a colleague who uses MikTeX with WinEdt and who told me that
> he didn't change PATH manually to show me the value of PATH on his
> computer and it included an entry for MikTeX's bin directory. Also,
> MikTeX's installation instructions suggest to run latex on a file from
> the Windows prompt which is likely to fail if latex is not in PATH.
I installed MikTeX on two PC in august/september 2005, and there I
hadn't an entry in PATH. Perhaps because I installed as user without
any admin rights.
>> At the
>> installation auctex did ask me for the path and make/configure etc did
>> seem to check the binaries.
>
> There is no configuration if you download the Emacs/AUCTeX bundle.
> You simply unpack it at the desired location and can start using it
> ... if PATH is set up correctly. (c;
I used the version at ourcomments.org and installed auctex separately.
Btw: what I really miss when I play around with emacs/auctex are
scripts like the ones winedt use to close and (re)open a pdf-file
before and after the pdfLaTeX run (it use dde messages).
Brian Elmegaard
> Btw: what I really miss when I play around with emacs/auctex are
> scripts like the ones winedt use to close and (re)open a pdf-file
> before and after the pdfLaTeX run (it use dde messages).
This is a big annoyance with acroread. There are two solutions:
1) Use gsview as pdf previewer
2) Use the hack by Jesper Harder (which I never got to try myself):
http://groups.google.com/groups?q=acrobat-close-all-docs&start=0&scoring=d&ie=UTF-8&
Ulrich M. Schwarz
[...]
> Btw: what I really miss when I play around with emacs/auctex are
> scripts like the ones winedt use to close and (re)open a pdf-file
> before and after the pdfLaTeX run (it use dde messages).
I have a very vague memory of some tool that can do it from the
command line. At that point, someone brave enough to run Talcum only
needs to point talcum-prod-commands at it. Alas, so many pending
features, but so many other things to do...
Ulrich
--
http://talcum.sarovar.org/ (Current release: 0.5.138 20050911)
Ulrike Fischer
> Ulrike Fischer <ne...@nililand.de> writes:
>
>> Btw: what I really miss when I play around with emacs/auctex are
>> scripts like the ones winedt use to close and (re)open a pdf-file
>> before and after the pdfLaTeX run (it use dde messages).
>
> This is a big annoyance with acroread. There are two solutions:
three: I can use winedt instead of emacs ;-)
> 1) Use gsview as pdf previewer
Yes, but it miss lot of things I need like copy&paste, search,
bookmarks, links, ....
> 2) Use the hack by Jesper Harder (which I never got to try myself):
> http://groups.google.com/groups?q=acrobat-close-all-docs&start=0&scorin
> g=d&ie=UTF-8&
I had found it. But it close all pdf in the reader, and it doesn't
address the "open part": when I reopen the pdf via winedt I get to the
page I had viewed last (as long as winedt has closed the pdf).
The scripts of winedt are rather sophisticated: It tries to find out
what acrobat is on the system and adapt the messages accordingly and
other things.