Discussion:
[ Re: Problem with MS Windows-based Installation]
Ciaran Taylor
2005-03-12 11:04:50 UTC
Permalink
Hi Folks,
Your instructions in INSTALL.WINDOWS may have missed a serious issue.
Auctex-11.55 uses "xdvi" for displaying DVI. On a MS windows-based machine,
xdvi is not available. I think most people uses MiKTeX which gives us "yap".
I tried to do a quick fix in tex.el but found use of other X-window
based programs
such as xpdf. Simply put, Auctex-11.55 is NOT for MS windows-based machines.
I wish you have made that clear in your release note.
regards,
Jun
If you read

INSTALL.WINDOWS as far as point 9, then what you find is:


9. For GNU Emacs, the recommended way to activate AUCTeX is to add the
following line to your `.emacs' file:

(require 'tex-site)

The configuration for Windows systems is probably not quite
fitting. Instead of loading `tex-site.el' in that manner, you
might want to load `tex-mik.el' (for MikTeX) or `tex-fptex' (for
fpTeX) instead.

I'm using AUCTeX 11.55 on Windows XP Pro using (require 'tex-site) in my
.emacs and it calls YAP just fine, as does C-c C-v. There is nothing
wrong with the AUCTeX installation instructions.

By the way I'm also running preview-latex 0.9 on GNU Emacs 21.3.50.1
(i386-mingw-nt5.1.2600) of 2005-01-30 on NONIQPC which I qot from
http://nqmacs.sourceforge.net/. That's working well (since I realised a
few things). There have been a few crashes: I'm not sure whether to
blame the CVS emacs, AUCTeX 11.55 or preview-latex 0.9.


Ciaran Taylor.
Ciaran Taylor
2005-03-12 11:08:01 UTC
Permalink
Post by Ciaran Taylor
Hi Folks,
Your instructions in INSTALL.WINDOWS may have missed a serious issue.
Auctex-11.55 uses "xdvi" for displaying DVI. On a MS windows-based machine,
xdvi is not available. I think most people uses MiKTeX which gives us "yap".
I tried to do a quick fix in tex.el but found use of other X-window
based programs
such as xpdf. Simply put, Auctex-11.55 is NOT for MS windows-based machines.
I wish you have made that clear in your release note.
regards,
Jun
If you read
9. For GNU Emacs, the recommended way to activate AUCTeX is to add the
(require 'tex-site)
The configuration for Windows systems is probably not quite
fitting. Instead of loading `tex-site.el' in that manner, you
might want to load `tex-mik.el' (for MikTeX) or `tex-fptex' (for
fpTeX) instead.
I'm using AUCTeX 11.55 on Windows XP Pro using (require 'tex-site) in
my .emacs and it calls YAP just fine, as does C-c C-v. There is
nothing wrong with the AUCTeX installation instructions.
By the way I'm also running preview-latex 0.9 on GNU Emacs 21.3.50.1
(i386-mingw-nt5.1.2600) of 2005-01-30 on NONIQPC which I qot from
http://nqmacs.sourceforge.net/. That's working well (since I realised
a few things). There have been a few crashes: I'm not sure whether
to blame the CVS emacs, AUCTeX 11.55 or preview-latex 0.9.
Ciaran Taylor.
That should have said "using (require 'tex-mik) in my .emacs"

(Blushes)
David Kastrup
2005-03-12 11:18:34 UTC
Permalink
Post by Ciaran Taylor
By the way I'm also running preview-latex 0.9 on GNU Emacs 21.3.50.1
(i386-mingw-nt5.1.2600) of 2005-01-30 on NONIQPC which I qot from
http://nqmacs.sourceforge.net/. That's working well (since I
realised a few things). There have been a few crashes: I'm not sure
whether to blame the CVS emacs, AUCTeX 11.55 or preview-latex 0.9.
Honest-to-God crashes are always to be blamed on CVS Emacs (or C
libraries it links with): Elisp provides a sandbox that should not let
applications like AUCTeX or preview-latex produce a crash, no matter
what they do.

Particularly relevant for preview-latex would be

2005-03-02 Kim F. Storm <***@cua.dk>

* dispextern.h (XASSERTS): Define to 0 if not already defined.
(xassert) [!XASSERTS]: Define dummy version.

[...]

2005-02-02 Miles Bader <***@gnu.org>

* dispextern.h (xassert): Enable unconditionally.

Any CVS Emacs built straight from HEAD from between those two dates is
definitely a particularly bad idea to use with preview-latex, or
overtall lines in general.

Now this would (by a hair's line) not apply to the Emacs you used, so
it might be some other bug. There are still some of those being fixed
these days, so it might help checking out the next nqmacs when it
becomes available (but no build from before 2005-03-02).
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Loading...