[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[AUCTeX-diffs] Changes to auctex/doc/wininstall.texi
From: |
David Kastrup |
Subject: |
[AUCTeX-diffs] Changes to auctex/doc/wininstall.texi |
Date: |
Wed, 08 Jun 2005 18:54:03 -0400 |
Index: auctex/doc/wininstall.texi
diff -u auctex/doc/wininstall.texi:1.20 auctex/doc/wininstall.texi:1.21
--- auctex/doc/wininstall.texi:1.20 Sat May 21 12:56:28 2005
+++ auctex/doc/wininstall.texi Wed Jun 8 22:54:01 2005
@@ -25,7 +25,7 @@
whole path in @samp{"double quote marks"} whenever you specify it on a
command line.
-Avoid `helpful' file names like @samp{/cygdrive/c} and
+Avoid `helpful' magic file names like @samp{/cygdrive/c} and
@samp{C:\PROGRA~1\} like the plague. It is quite unlikely that the
scripts will be able to identify the actual file names involved. Use
the full paths, making use of normal Windows drive letters like
@@ -43,13 +43,13 @@
destination, and you can ultimately remove the directory where you
unpacked the files.
-The distribution contains only text files, and their line endings have
-to be proper for Windows, or you'll likely run into problems later on.
-Your unpacking tool probably has options for achieving this effect.
-Your chances might be better if you are using the @samp{.zip} archive
-rather than the @samp{.tar.gz} file. If you are loading files from the
-distribution into Emacs, its mode line should show the @samp{(DOS)}
-indicator.
+Line endings are a problem under Windows. The distribution contains
+only text files, and theoretically most of the involved tools should get
+along with that. However, the files are processed by various utilities,
+and it is conceivable that not all of them will use the same line ending
+conventions. If you encounter problems, it might help if you try
+unpacking (or checking out) the files in binary mode, if your tools
+allow that.
If you don't have a suitable unpacking tool, skip to the next step: this
should provide you with a working @samp{unzip} command.
@@ -139,25 +139,25 @@
@item --with-emacs
if you are installing for a version of Emacs. You can use
address@hidden@var{/path/to/emacs}} to specify the name of the
address@hidden@var{drive:/path/to/emacs}} to specify the name of the
installed Emacs executable, complete with its path if necessary (if
Emacs is not within a directory specified in your @env{PATH} environment
setting).
@item --with-xemacs
if you are installing for a version of XEmacs. Again, you can use
address@hidden@var{/path/to/xemacs}} to specify the name of the
address@hidden@var{drive:/path/to/xemacs}} to specify the name of the
installed XEmacs executable complete with its path if necessary. It may
also be necessary to specify this option if a copy of Emacs is found in
your @env{PATH} environment setting, but you still would like to install
a copy of @AUCTeX{} for XEmacs.
address@hidden address@hidden/dir}
address@hidden address@hidden:/dir}
is an XEmacs-only option giving the location of the package directory.
This will install and activate the package. Emacs uses a different
installation scheme:
address@hidden address@hidden/path/to/site-lisp}
address@hidden address@hidden:/path/to/site-lisp}
This Emacs-only option tells a place in @code{load-path} below which the
files are situated. The startup files @file{auctex.el} and
@file{preview-latex.el} will get installed here unless a subdirectory
@@ -174,7 +174,7 @@
@ref{Configure}.
@end ifclear
address@hidden address@hidden/dir}
address@hidden address@hidden:/dir}
Directory containing automatically generated information. You should
not normally need to set this, as @samp{--prefix} should take care of
this.
@@ -184,7 +184,7 @@
display. This will be the case if you are using a native variant of
@w{Emacs 21}.
address@hidden address@hidden
address@hidden address@hidden:dir}
This will specify the directory where your @TeX{} installation sits. If
your @TeX{} installation does not conform to the TDS (@TeX{} directory
standard), you may need to specify more options to get everything in
@@ -207,7 +207,7 @@
idea, but you can get around by specifying environment variables to
@file{configure}:
@example
-GS="@var{/path/to/gswin32c.exe}" ./configure @dots{}
+GS="@var{drive:/path/to/gswin32c.exe}" ./configure @dots{}
@end example
should work for this purpose. @file{gswin32c.exe} is the usual name for
the required @emph{command line} executable under Windows; in contrast,
- [AUCTeX-diffs] Changes to auctex/doc/wininstall.texi,
David Kastrup <=