Mercurial > emacs
view BUGS @ 103765:7390f2dfe6b8
Standardize the way M-x commands are written:
dashes inside command names, not spaces; spaces before <Return>.
(Summary): Describe the new behavior of C-l.
(Basic Cursor Control): Don't say that files "ought" to end in newlines.
Try to distinguish scroll bar from fringes.
You can also scroll with a wheel mouse.
(If Emacs Stops Responding): Rename from "When Emacs is hung".
(Inserting And Deleting): Continuation marks appear in the fringe.
Clarify that deletion can be undone. Mention cut and paste, and the Glossary.
(Files, Mode Line): Update mode-line format.
(Extending The Command Set): Downplay C-z, since using Emacs on a
text-only terminal is less common these days.
(Searching): Incremental searching is no longer atypical.
Downplay flow control issues, remove reference to deleted FAQ node.
(Multiple Windows): Mention frames.
(Multiple Frames): New section.
(Getting More Help): Downplay C-h having a different binding.
Don't say help is "on-line", since the meaning has changed.
(More Features): Replace "on-line". Use C-h rather than F10 h.
Say a little more about completion.
(Conclusion): Don't mention C-z again here.
author | Glenn Morris <rgm@gnu.org> |
---|---|
date | Wed, 08 Jul 2009 02:31:02 +0000 |
parents | fb8bf24d2eb9 |
children | ac52af4a044c |
line wrap: on
line source
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. There are three ways to read the Bugs section. (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. (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.) (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.