Mercurial > emacs
view BUGS @ 105957:25e1d7e37015
* widget.el (define-widget): Purecopy the docstring.
* international/mule-cmds.el (charset): Do not purecopy the
docstring here, define-widget does it.
* textmodes/texinfo.el (texinfo-open-quote, texinfo-close-quote):
* textmodes/bibtex-style.el (auto-mode-alist):
* progmodes/inf-lisp.el (inferior-lisp-prompt):
* progmodes/compile.el (compile-command):
* language/korea-util.el (default-korean-keyboard):
* international/mule-conf.el (file-coding-system-alist):
* emacs-lisp/eldoc.el (eldoc-minor-mode-string):
* tooltip.el (tooltip-frame-parameters):
* newcomment.el (comment-end, comment-padding):
* dired.el (dired-trivial-filenames):
* comint.el (comint-file-name-prefix): Purecopy initial values.
author | Dan Nicolaescu <dann@ics.uci.edu> |
---|---|
date | Wed, 11 Nov 2009 19:24:20 +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.