Mercurial > hg > xemacs-beta

view BUGS @ 1378:69a674f5861f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2003-03-24 16:30:55 by youngs] 2003-03-25 Steve Youngs <youngs@xemacs.org> * package-admin.el: (package-admin-delete-binary-package): Only delete the lisp directory if it exists. (package-admin-find-top-directory): New. (package-admin-get-install-dir): Use it. * package-get.el (package-get-install-to-user-init-directory): New. If non-nil install packages under `user-init-directory'. (package-get): `package-admin-get-install-dir' only takes 2 args. * package-ui.el (pui-install-selected-packages): The 2nd arg to `package-admin-get-install-dir' is optional, no need to specify nil.
author youngs
date Mon, 24 Mar 2003 16:30:56 +0000
parents 9f59509498e1
children
line wrap: on
line source

If you think you may have found a bug in XEmacs, please
read the Bugs section of the XEmacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the XEmacs manual.

(2) With Info.  Start XEmacs, do C-h i to enter Info,
then m XEmacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the XEmacs distribution.)

(3) By hand.  Do
    cat info/xemacs* | more "+/^File: xemacs.info,  Node: Bugs,"


Part II of the XEmacs FAQ, available in a manner similar to the above,
or via the world wide web, contains extensive information on how to
track down and report bugs.

	http://www.xemacs.org/faq/