Mercurial > emacs
view BUGS @ 90283:9970a9645ad9
Revision: emacs@sv.gnu.org/emacs--unicode--0--patch-4
Creator: Stefan Monnier <monnier@iro.umontreal.ca>
Merge tar-mode changes from the trunk.
* tar-mode.el: Merge changes from the trunk:
(tar-header-block-tokenize): Tighten regexp.
(tar-summarize-buffer): Don't clear the modified-p bit if it wasn't
cleared before. Obey default-enable-multibyte-characters. Use mapconcat.
(tar-mode-map): Move initialization inside delcaration.
(tar-alter-one-field): Don't hardcode point-min==1.
author | Miles Bader <miles@gnu.org> |
---|---|
date | Sat, 21 Jan 2006 06:45:38 +0000 |
parents | 8ce686bd7f4f |
children | fb8bf24d2eb9 |
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-e in Emacs) to make sure it isn't a known issue.