[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [AUCTeX] Pre-compiled CVS Emacs with AUCTeX for Windows

From: Harald von Aschen
Subject: Re: [AUCTeX] Pre-compiled CVS Emacs with AUCTeX for Windows
Date: Sat, 15 Oct 2005 12:39:44 +0200

At 21:10 12.10.05 +0200, Ralf Angeli wrote:

Hi Ralf!

a pre-compiled development version of Emacs including AUCTeX is now
available for Windows at <URL:>.
Release notes can be found in the file RELEASE-2005-10-12.txt in the
same directory.

As this is the first time we are providing such a package, feedback
about how people get along with it would be appreciated.  Also note
that this is to some extent experimental because a development version
of Emacs is involved.  This may require new releases of the package.
In such a case the old one is likely to disappear from the server.
Please consider this if you link to it.

Thank you very much for your work!

Here is my (short) experience with TeXLive on Windows 98/II, with an old 233 MHz Pentium:

Paths have to been set up properly in autoexec.bat (e.g. path to "gswin32c.exe") and then all is working fine. It it interesting that the color schemes for syntax highlighting are so different to my used 21.3.1 emacs version, these light colours are not readable (e.g. yellow or cyan or orange) and on the other hand for marking Emacs is using dark colors (like MediumBlue) for black characters. I haven't seen this problem before on Unix. O.k., let's look on *Messages*:

Unable to load color "SystemWindowText"
Unable to load color "SystemWindow"
Loading tool-bar...
Unable to load color "SystemWindow"
Unable to load color "SystemWindowText"
Unable to load color "systembuttonface"
Unable to load color "systembuttontext"
Loading tool-bar...done
Loading image...done
Loading f:/DESKTOP/EMACSPRECOMPILED/EMACS+AUCTEX-W32-2005-10-12/EMACS/site-lisp/tex-site.el (source)...done
Unable to load color "SystemWindow"
Unable to load color "SystemWindowText"

But this might be a problem of this Emacs release.

Next, opening a LaTeX-file and generating previews is working fine but takes a long time for two pages of LaTeX-code on this old system here.

But now to the real problems:

Starting the preview cmdproxy.exe is opened and keep alive. And a "winoldap" (WINOA386.MOD) is in the task manager. O.k., changing some source code and calling "toggle at point" shows the preview just fine after some time but a new "winoldapp" process is listed in the task manager. O.k., now I have just played around and called some more times "toggle at point" for generating previews. This ends in now 6 "winoldap" applications not being closed!

Every time I was calling "toggle at point" I was asked if I want to cache the document's preamble. First time as a menu and then only in the minibuffer window.

When I want to exit Emacs a question is arising: process "Preview-LaTeX" is running, shall I kill it? But the "winoldapp" processes are not killed and I'm not able to kill them by hand, a hint from Windows is popping up "Windows can't close this application automatically" (or something like that correctly translated from German). "Would you like to close this application and all data not stored will be lost?" After clicking on "yes" the process is still not killed, even killing it with the task manager brings no effect. Not surprisingly after that it is not possible to shut down the Windows 98 system without a crash.

Other curious error message is:

* Calling Preview Latex with (or toggle) at point the first time on a new opened document results in:

  Running `Preview-LaTeX' on `ueb03' with ``latex -ini "&latex" \
  prv_ueb03.ini \
  "\nonstopmode\nofiles\PassOptionsToPackage{active, \
  tightpage,auctex}{preview}\AtBeginDocument{\ifx\ifPreview \
  \undefined\RequirePackage[displaymath,floats,graphics, \
  textmath,sections,footnotes]{preview}[2004/11/05]\fi} \
  Angegebenes COMMAND-Verzeichnis ist falsch

  Microsoft(R) Windows 98
   (C)Copyright Microsoft Corp 1981-1999.


(Angegebenes Command-Verzeichnis ist falsch = the path to COMMAND is wrong.)

After calling this command again all is working fine.

Hope this helps!

Best regards


reply via email to

[Prev in Thread] Current Thread [Next in Thread]