Mercurial > emacs
view BUGS @ 48135:2c6154347319
(Info-streamline-headings): New var.
(Info-dir-remove-duplicates): New fun.
(Info-insert-dir): Use it. Simplify the code with push,mapc,dolist.
(Info-select-node): Simplify handling of Info-header-line.
(Info-forward-node): Undo 2000/12/15 since we don't narrow any more.
(Info-mode): Set header-line-format once and for all.
(Info-fontify-node): Accept bogus first line with `File:' missing.
Only make first line invisible if Info-use-header-line.
Don't use `intangible': it's evil. Use inhibit-read-only.
(Info-follow-reference, Info-next-reference, Info-prev-reference)
(Info-try-follow-nearest-node): Don't bind inhibit-point-motion-hooks
since we don't use intangible any more.
author | Stefan Monnier <monnier@iro.umontreal.ca> |
---|---|
date | Sun, 03 Nov 2002 12:01:33 +0000 |
parents | af68d12218d0 |
children | 8ce686bd7f4f |
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 P in Emacs) to make sure it isn't a known issue.