Mercurial > hg > xemacs-beta
view BUGS @ 2481:505a24c07ba9
[xemacs-hg @ 2005-01-15 15:17:32 by michaels]
2005-01-08 Mike Sperber <mike@xemacs.org>
* packages.el (packages-find-installation-package-directories): Add.
* find-paths.el (paths-for-each-emacs-directory): Abstract FUNC
parameter out of `paths-find-emacs-directory'.
(paths-find-emacs-directories): Add.
(paths-find-emacs-directory): Redefine in terms of
`paths-for-each-emacs-directory'.
(paths-for-each-site-directory): Add.
(paths-find-site-directory): Redefine in terms of
`paths-for-each-site-directory'.
(paths-find-site-directories): Add.
(paths-for-each-version-directory): Add.
(paths-find-version-directory): Redefine in terms of
`paths-for-each-version-directory'.
(paths-find-version-directories): Add.
author | michaels |
---|---|
date | Sat, 15 Jan 2005 15:17:36 +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/