mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-11-21 06:55:39 +00:00
* BUGS, INSTALL.BZR: Updates.
This commit is contained in:
parent
fdb893e712
commit
6c3ab469a4
31
BUGS
31
BUGS
@ -1,26 +1,23 @@
|
||||
If you think you may have found a bug in GNU Emacs, please
|
||||
read the Bugs section of the Emacs manual for advice on
|
||||
If you think you may have found a bug in GNU Emacs, please read the
|
||||
Bugs section of the Emacs 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.
|
||||
(2) how to write a useful bug report and what information it needs to have.
|
||||
|
||||
There are three ways to read the Bugs section.
|
||||
You can read the read the Bugs section of the manual from inside Emacs.
|
||||
Start Emacs, do C-h i to enter Info, then m Emacs RET to get to the
|
||||
Emacs manual, then m Bugs RET to get to the section on bugs.
|
||||
Or you can use the standalone Info program in a like manner.
|
||||
(Standalone Info is part of the Texinfo distribution, not part of the
|
||||
Emacs distribution.)
|
||||
|
||||
(1) In a printed copy of the Emacs manual.
|
||||
You can order one from the Free Software Foundation;
|
||||
see the file etc/ORDERS. But if you don't have a copy on
|
||||
hand and you think you have found a bug, you shouldn't wait
|
||||
to get a printed manual; you should read the section right away
|
||||
as described below.
|
||||
Printed copies of the Emacs manual can be purchased from the Free
|
||||
Software Foundation's online store at <http://shop.fsf.org/>.
|
||||
|
||||
(2) With Info. Start Emacs, do C-h i to enter Info,
|
||||
then m Emacs 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 Emacs distribution.)
|
||||
If necessary, you can read the manual without an info program:
|
||||
|
||||
(3) By hand. Do
|
||||
cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
|
||||
|
||||
|
||||
Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to
|
||||
make sure it isn't a known issue.
|
||||
|
@ -1,3 +1,7 @@
|
||||
2010-10-12 Glenn Morris <rgm@gnu.org>
|
||||
|
||||
* BUGS, INSTALL.BZR: Updates.
|
||||
|
||||
2010-10-08 Eli Zaretskii <eliz@gnu.org>
|
||||
|
||||
* make-dist: Don't distribute src/buildobj.h. (Bug#7167)
|
||||
|
14
INSTALL.BZR
14
INSTALL.BZR
@ -31,13 +31,9 @@ generated files, such as esh-groups.el, and *-loaddefs.el in some
|
||||
subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be
|
||||
updated to reflect new autoloaded functions. If you see errors (rather
|
||||
than warnings) about undefined lisp functions during compilation, that
|
||||
may be the reason. Another symptom may be an error saying that
|
||||
"loaddefs.el" could not be found; this is due to a change in the way
|
||||
loaddefs.el was handled in version control, and should only happen
|
||||
once, for users that are updating old sources. Finally, sometimes
|
||||
there can be build failures related to *loaddefs.el (e.g. "required
|
||||
feature `esh-groups' was not provided"). In that case, follow the
|
||||
instructions below.
|
||||
may be the reason. Finally, sometimes there can be build failures
|
||||
related to *loaddefs.el (e.g. "required feature `esh-groups' was not
|
||||
provided"). In that case, follow the instructions below.
|
||||
|
||||
To update loaddefs.el (and similar files), do:
|
||||
|
||||
@ -53,10 +49,6 @@ platform-specific configuration scripts (nt/configure.bat, config.bat,
|
||||
etc.) before "make bootstrap" or "make"; the rest of the procedure is
|
||||
applicable to those systems as well.
|
||||
|
||||
Questions, requests, and bug reports about the Bazaar versions of Emacs
|
||||
should be sent to bug-gnu-emacs@gnu.org rather than gnu.emacs.help.
|
||||
Ideally, use M-x report-emacs-bug RET.
|
||||
|
||||
Because the Bazaar version of Emacs is a work in progress, it will
|
||||
sometimes fail to build. Please wait a day or so (and check the bug
|
||||
and development mailing list archives) before reporting such problems.
|
||||
|
Loading…
Reference in New Issue
Block a user