`-no-init-file'
`-q'
- Do not load your Emacs init file `~/.emacs'.
+ Do not load your Emacs init file. *Note Init File::.
`-no-site-file'
Do not load the site-specific init file `lisp/site-start.el'.
This is equivalent to `-q -no-site-file -no-early-packages'.
`-user-init-file FILE'
- Load FILE as your Emacs init file instead of `~/.emacs'.
+ Load FILE as your Emacs init file instead of
+ `~/.xemacs/init.el'/`~/.emacs'.
`-user-init-directory DIRECTORY'
Use DIRECTORY as the location of your early package hierarchies
`-user USER'
`-u USER'
- Equivalent to `-user-init-file ~USER/.emacs -user-init-directory
- ~USER/.xemacs'.
+ Equivalent to `-user-init-file ~USER/.xemacs/init.el
+ -user-init-directory ~USER/.xemacs', or `-user-init-file
+ ~USER/.emacs -user-init-directory ~USER/.xemacs'. whichever init
+ file comes first. *Note Init File::.
Note that the init file can get access to the command line argument
values as the elements of a list in the variable `command-line-args'.
Emacs only.
\1f
-File: xemacs.info, Node: Startup Paths, Next: Basic, Prev: Command Switches, Up: Top
+File: xemacs.info, Node: Startup Paths, Next: Packages, Prev: Command Switches, Up: Top
How XEmacs finds Directories and Files
======================================
the one where it is being built.) Such a directory containing a
hierarchy is called a "root". Whenever this section refers to a
directory using the shorthand `<root>', it means that XEmacs searches
-for it under all hierarchies under all hierarchies XEmacs was able to
-scrounge up. In a running XEmacs, the hierarchy roots are stored in
-the variable `emacs-roots'.
+for it under all hierarchies XEmacs was able to scrounge up. In a
+running XEmacs, the hierarchy roots are stored in the variable
+`emacs-roots'.
Package Hierarchies
-------------------
ones somewhere in the middle, and last hierarchies are (you guessed it)
last.
- By default, XEmacs expects an early package hierarchy in the a
-subdirectory `.xemacs' of the user's home directory.
+ By default, XEmacs expects an early package hierarchy in the
+subdirectory `.xemacs/xemacs-packages' of the user's home directory.
Moreover, XEmacs expects late hierarchies in the subdirectories
`site-packages', `mule-packages', and `xemacs-packages' (in that order)
By default, XEmacs does not have a pre-configured last package
hierarchy. Last hierarchies are primarily for using package hierarchies
of outdated versions of XEmacs as a fallback option. For example, it is
-possible to run XEmacs 21.0 with the 20.4 package hierarchy as a last
+possible to run XEmacs 21 with the 20.4 package hierarchy as a last
hierarchy.
It is possible to specify at configure-time the location of the
various package hierarchies with the `--package-path' option to
configure. The early, late, and last components of the package path
-are separated by double instead of single colons. If three components
-are present, they are locate the early, late, and last package
+are separated by double instead of single colons. If all three
+components are present, they locate the early, late, and last package
hierarchies respectively. If two components are present, they locate
the early and late hierarchies. If only one component is present, it
locates the late hierarchy. At run time, the package path may also be
package data directories as well as `data-directory'.
\1f
-File: xemacs.info, Node: Basic, Next: Undo, Prev: Startup Paths, Up: Top
+File: xemacs.info, Node: Basic, Next: Undo, Prev: Packages, Up: Top
Basic Editing Commands
**********************
menu.
XEmacs comes with many translations of tutorial. If your XEmacs is
-with MULE and you set up language environment correctly, XEmacs choses
+with MULE and you set up language environment correctly, XEmacs chooses
right tutorial when available (*note Language Environments::). If you
want specific translation, give `C-h t' a prefix argument, like `C-u
C-h t'.