emacs / BUGS

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.

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.)

Printed copies of the Emacs manual can be purchased from the Free
Software Foundation's online store at <>.

If necessary, you can read the manual without an info program:

    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.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.