The XEmacs 21 distribution comes only with a very basic set of
built-in modes and packages. Most of the packages that were part of
-the distribution of earlier versions of XEmacs are now separately
-available. The installer as well as the user can choose which
+the distribution of earlier versions of XEmacs are now available
+separately. The installer as well as the user can choose which
packages to install; the actual installation process is easy.
This gives an installer the ability to tailor an XEmacs installation for
local needs with safe removal of unnecessary code.
also listed on the @code{Options} menu under:
@example
- Options->Customize->Emacs->Packages
+ Options->Customize->Emacs->Packages
@end example
However, don't select any of these menu picks unless you actually want
access it via the menus:
@example
- Options->Manage Packages->List & Install
+ Options->Manage Packages->List & Install
@end example
Or, you can get to it via the keyboard:
idea to install all packages and not interfere with the wishes of your
users.
+If you can't find which package provides the feature you require, try
+using the @code{package-get-package-provider} function. Eg., if you know
+that you need @code{thingatpt}, type:
+
+@example
+M-x package-get-package-provider RET thingatpt
+@end example
+
+which will return something like (fsf-compat "1.06"). You can the use
+one of the methods above for installing the package you want.
+
@subsection XEmacs and Installing Packages
Normally, packages are installed over the network, using EFS
already have some or all of the packages on a local disk, such as a
CDROM. If you want to install from a local disk, you must first tell
XEmacs where to find the package binaries. This is done by adding a line
-like the following to your @file{.emacs} file:
+like the following to your init file:
@example
(setq package-get-remote (cons (list nil "/my/path/to/package/binaries")
package-get-remote))
@end example
+@xref{Init File}.
+
Here, you'd change @file{/my/path/to/package/binaries} to be the path
to your local package binaries. Next, restart XEmacs, and you're ready
to go (advanced users can just re-evaluate the sexp).
add these directory names to @code{package-get-remote} using:
@example
- M-x pui-add-install-directory
+ M-x pui-add-install-directory
@end example
Note, however, that any directories added using this function are not
browser and installer, using the menu pick:
@example
- Options->Manage Packages->List & Install
+ Options->Manage Packages->List & Install
@end example
or
@example
- Options->Manage Packages->Using Custom->Select-> ...
+ Options->Manage Packages->Using Custom->Select-> ...
@end example
You can also access it using the keyboard:
customize menus, under:
@example
- Options->Customize->Emacs->Packages-> ...
+ Options->Customize->Emacs->Packages-> ...
@end example
or
@example
- Options->Manage Packages->Using Custom->Select-> ...
+ Options->Manage Packages->Using Custom->Select-> ...
@end example
Set their state to on, and then do:
@example
- Options->Manage Packages->Using Custom->Update Packages
+ Options->Manage Packages->Using Custom->Update Packages
@end example
This will automatically retrieve the packages you have selected from the
@subsection Manual Binary Package Installation
Pre-compiled, binary packages can be installed in either a system
-package directory (this is determined when XEmacs is compiled), or in a
-subdirectory of your @file{$HOME} directory:
+package directory (this is determined when XEmacs is compiled), or in
+one of the following
+subdirectories of your @file{$HOME} directory:
@example
-~/.xemacs/packages
+~/.xemacs/mule-packages
+~/.xemacs/xemacs-packages
@end example
+Packages in the former directory will only be found by a Mule-enabled
+XEmacs.
+
XEmacs does not have to be running to install binary packages, although
XEmacs will not know about any newly-installed packages until you
restart XEmacs. Note, however, that installing a newer version of a
will typically be a gzip'd tarball.
@item
-Decide where to install the packages: in the system package directory,
-or in @file{~/.xemacs/packages}. If you want to install the
-packages in the system package directory, make sure you can write into
-that directory. If you want to install in your @file{$HOME} directory,
-create the directory, @file{~/.xemacs/packages}.
+Decide where to install the packages: in the system package
+directory, or in @file{~/.xemacs/mule-packages} or
+@file{~/.xemacs/xemacs-packages}, respectively. If you want to install
+the packages in the system package directory, make sure you can write
+into that directory. If you want to install in your @file{$HOME}
+directory, create the directory, @file{~/.xemacs/mule-packages} or
+@file{~/.xemacs/xemacs-packages}, respectively.
@item
Next, @code{cd} to the directory under which you want to install the
typically do this using the commands:
@example
- gunzip < package.tar.gz | tar xvf -
+ gunzip < package.tar.gz | tar xvf -
@end example
Above, replace @file{package.tar.gz} with the filename of the
Of course, if you use GNU @code{tar}, you could also use:
@example
- tar xvzf package.tar.gz
+ tar xvzf package.tar.gz
@end example
@comment What about native MS Windows users???
projects / chise / xemacs-chise.git.1 / blobdiff