Mercurial > emacs
view BUGS @ 106793:f0cdc68631e2
Fix typos in ffap.el.
* ffap.el (ffap-shell-prompt-regexp, ffap-all-subdirs, ffap-url-p)
(ffap-alist, ffap-tex-path, ffap-url-at-point, ffap-gopher-regexp)
(ffap-gopher-at-point, ffap-file-at-point, ffap-read-file-or-url)
(ffap-read-url-internal, ffap-menu, ffap-at-mouse):
Fix typos in docstrings.
(ffap-url-regexp): Doc fix.
(ffap-at-mouse): Fix typo in message.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Mon, 11 Jan 2010 16:22:23 +0100 |
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.