xemacs-beta: man/xemacs-faq.texi comparison

comparison man/xemacs-faq.texi @ 5495:1f0b15040456

Merge.

author	Aidan Kehoe <kehoea@parhasard.net>
date	Sun, 01 May 2011 18:44:03 +0100
parents	593d9f73a7e8
children	40a52efbf3a3

comparison

equal deleted inserted replaced

-:861f2601a38b
+:1f0b15040456
 * Q2.5.2::    Startup problems related to paths or package locations.
 * Q2.5.3::    XEmacs won't start without network, or starts slowly.
 * Q2.5.4::    Startup warnings about deducing proper fonts?
 * Q2.5.5::    Warnings from incorrect key modifiers.
 * Q2.5.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+* Q2.5.7::    XEmacs issues messages about ``auto-autoloads already loaded.''
 3 Editing Functions
 3.0: The Keyboard
 * Q3.0.1::    How can I customize the keyboard?
 and was also the last version without international language support.
 @node Q1.0.3, Q1.0.4, Q1.0.2, Introduction
 @unnumberedsubsec Q1.0.3: How do you pronounce XEmacs?
-The most common pronounciation is @samp{Eks eemax}, @samp{Eks'im&ks} in
+The most common pronunciation is @samp{Eks eemax}, @samp{Eks'im&ks} in
 Kirshenbaum IPA. (See
 @uref{http://www.kirshenbaum.net/IPA/ascii-ipa.pdf} if you know the IPA
 already and want to know how to map from Kirshenbaum to it.)
 @node Q1.0.4, Q1.0.5, Q1.0.3, Introduction
 @item erc
 ERC is an Emacs InternetRelayChat client.
 @item escreen
-Multiple editing sessions withing a single frame (like screen).
+Multiple editing sessions within a single frame (like screen).
 @item eshell
 Command shell implemented entirely in Emacs Lisp.
 @item ess
 * Q2.5.2::    Startup problems related to paths or package locations.
 * Q2.5.3::    XEmacs won't start without network, or starts slowly.
 * Q2.5.4::    Startup warnings about deducing proper fonts?
 * Q2.5.5::    Warnings from incorrect key modifiers.
 * Q2.5.6::    XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
+* Q2.5.7::    XEmacs issues messages about ``auto-autoloads already loaded.''
 @end menu
 @unnumberedsec 2.0: Installation (General)
 @node Q2.0.1, Q2.0.2, Installation, Installation
 Please see the @file{PROBLEMS} file that comes with XEmacs (it's in
 the top-level source directory) to read what it says about your
 platform.
-If you compiled XEmacs 21.4 or ealier using @samp{--use-union-type}, or
+If you compiled XEmacs 21.4 or earlier using @samp{--use-union-type}, or
 21.5 or later using @samp{--enable-union-type} (or in either case used
 the option @samp{USE_UNION_TYPE} in @file{config.inc} under Windows),
 try recompiling again without it.  The union type has been known to
 trigger compiler errors in a number of cases.
 keysym Meta_R = Mode_switch
 add mod2 = Mode_switch
 EOF
 @end example
-@node Q2.5.6,  , Q2.5.5, Installation
+@node Q2.5.6, Q2.5.7, Q2.5.5, Installation
 @unnumberedsubsec Q2.5.6: XEmacs 21.1 on Windows used to spawn an ugly console window on every startup.  Has that been fixed?
 Yes.
 The console was there because @file{temacs} (and in turn, @file{xemacs})
 signals to a child process, and because of the bogosity mentioned above
 with GUI programs and the standard command shell.  Currently, XEmacs
 just creates and immediately hides a console when necessary, and
 works around the "no useful stdio" problem by creating its own console
 window as necessary to display messages in.)
+@node Q2.5.7,  , Q2.5.6, Installation
+@unnumberedsubsec Q2.5.7: XEmacs issues messages about ``auto-autoloads already loaded.''
+On Sat, 05 Mar 2011 11:54:47 -0500, in Message-ID:
+<4D726AD7.7020303@@gmail.com> on xemacs-beta, Raymond Toy reported:
+@quotation
+[N]ow every time I start xemacs, I get 100+ error messages stating that
+the auto-autoload for every package has already been loaded.
+@end quotation
+This occurs if you have duplicate packages installed on your load-path.
+To detect exactly which paths are duplicated, use @kbd{M-x
+list-load-path-shadows}.  If you have a small number of duplicated
+libraries, it is probably one or more packages available both in the
+XEmacs distribution and in third-party distributions.  If you prefer the
+third-party version, use @kbd{M-x list-packages} to get the package
+management UI, and uninstall the particular packages.  Removal of third
+party packages must be done manually, if you wish to keep the version
+distributed by XEmacs.
+When you have many duplicate packages, a common cause is that XEmacs
+finds @emph{package root directories} that are duplicates of each other.
+This can occur in some automounter configurations, or when the roots
+share some subtrees via symlinks.  In this case, you will get a warning
+for @emph{all} of the packages you have installed.  Although this is
+basically a site configuration problem, please report these cases.
+XEmacs is already aware of many automounter artifacts, and automatically
+adjusts for them.  Code is being added to try to detect symlinks.  We
+may not be able to handle every case, but we'd like to know about them,
+and where possible incorporate workarounds.
+Package root directories are specified at configuration time via the
+@code{--prefix}, @code{--exec-prefix}, and the @samp{--with-*-packages}
+options; at runtime relative to the XEmacs binary (@file{../share} and
+@file{..} (for run-in-place)); and at runtime via the
+@samp{EMACS*PACKAGES} environment variables.  Unless you have special
+needs, it is best to install XEmacs and the packages (configuring with
+@code{--with-prefix=$prefix} for XEmacs and by untarring the SUMOs in
+@file{@code{$prefix}/share/xemacs/}.
+Note that older versions of XEmacs (21.1, 21.4, and early releases of
+21.5) by default expect the packages to be installed under
+@file{@code{$prefix}/lib} rather than @file{@code{$prefix}/share}.  See
+the documentation for @file{configure} for how to point XEmacs at
+@file{@code{$prefix}/share/xemacs/} if that is preferred, or older
+XEmacsen need to share packages with recent versions.
 @node Editing, Display, Installation, Top
 @unnumbered 3 Editing Functions
 This is part 3 of the XEmacs Frequently Asked Questions list.  This
 You may see an unreasonable diff (often large) that doesn't seem to
 reflect your work.
 This is usually due to using @code{hg diff} on a @dfn{merge commit}.
 That means the commit has multiple parents, and joins together two lines
-of development that occured concurrently.
+of development that occurred concurrently.
 You're diffing against the "wrong" one; try the other one.  You get the
-relevent revision number or ID from @code{hg log}.  In more detail:
+relevant revision number or ID from @code{hg log}.  In more detail:
 When there is a merge in Mercurial, it will often be the case that
 one of the parents is the immediate predecessor of the merge
 commit.  @code{hg log} will report something like
 Once upon a time, an XEmacs developer wrote:
 > GAAAAK!  What's the best way to restore ChangeLog and its history?
-He had just inadvertantly pushed a commit which deleted
+He had just inadvertently pushed a commit which deleted
 @file{src/ChangeLog}!  The history is still there, not to worry.  (In
 this case, another developer had restored src/ChangeLog already.)  The
 best way depends on a number of things.  First, let's look at the log
 and the state of the DAG (the graph of commits).  Here's the log,
 formatted somewhat differently from the usual output for compactness.

Mercurial > hg > xemacs-beta

comparison man/xemacs-faq.texi @ 5495:1f0b15040456