Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
6c3ab469
Commit
6c3ab469
authored
Oct 11, 2010
by
Glenn Morris
Browse files
* BUGS, INSTALL.BZR: Updates.
parent
fdb893e7
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
21 additions
and
28 deletions
+21
-28
BUGS
BUGS
+14
-17
ChangeLog
ChangeLog
+4
-0
INSTALL.BZR
INSTALL.BZR
+3
-11
No files found.
BUGS
View file @
6c3ab469
If you think you may have found a bug in GNU Emacs, please
If you think you may have found a bug in GNU Emacs, please read the
read the Bugs section of the Emacs manual for advice on
Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
(2) how to write a useful bug report and what information it needs to have.
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.
Printed copies of the Emacs manual can be purchased from the Free
You can order one from the Free Software Foundation;
Software Foundation's online store at <http://shop.fsf.org/>.
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.
(2) With Info. Start Emacs, do C-h i to enter Info,
If necessary, you can read the manual without an info program:
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.)
(3) By hand. Do
cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
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
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.
make sure it isn't a known issue.
ChangeLog
View file @
6c3ab469
2010-10-12 Glenn Morris <rgm@gnu.org>
* BUGS, INSTALL.BZR: Updates.
2010-10-08 Eli Zaretskii <eliz@gnu.org>
2010-10-08 Eli Zaretskii <eliz@gnu.org>
* make-dist: Don't distribute src/buildobj.h. (Bug#7167)
* make-dist: Don't distribute src/buildobj.h. (Bug#7167)
...
...
INSTALL.BZR
View file @
6c3ab469
...
@@ -31,13 +31,9 @@ generated files, such as esh-groups.el, and *-loaddefs.el in some
...
@@ -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
subdirectories of lisp/, e.g. mh-e/ and calendar/) will need to be
updated to reflect new autoloaded functions. If you see errors (rather
updated to reflect new autoloaded functions. If you see errors (rather
than warnings) about undefined lisp functions during compilation, that
than warnings) about undefined lisp functions during compilation, that
may be the reason. Another symptom may be an error saying that
may be the reason. Finally, sometimes there can be build failures
"loaddefs.el" could not be found; this is due to a change in the way
related to *loaddefs.el (e.g. "required feature `esh-groups' was not
loaddefs.el was handled in version control, and should only happen
provided"). In that case, follow the instructions below.
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.
To update loaddefs.el (and similar files), do:
To update loaddefs.el (and similar files), do:
...
@@ -53,10 +49,6 @@ platform-specific configuration scripts (nt/configure.bat, config.bat,
...
@@ -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
etc.) before "make bootstrap" or "make"; the rest of the procedure is
applicable to those systems as well.
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
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
sometimes fail to build. Please wait a day or so (and check the bug
and development mailing list archives) before reporting such problems.
and development mailing list archives) before reporting such problems.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment