Mercurial > emacs
view BUGS @ 100354:89bba37a3188
* progmodes/ruby-mode.el (ruby-mode-abbrev-table, ruby-mode-map)
(ruby-mode-syntax-table, ruby-indent-tabs-mode, ruby-indent-level)
(ruby-mode-variables, ruby-indent-line, ruby-indent-size)
(ruby-calculate-indent, ruby-electric-brace, ruby-beginning-of-defun)
(ruby-here-doc-beg-syntax, ruby-here-doc-end-syntax)
(ruby-font-lock-syntax-table, ruby-font-lock-keywords)
(ruby-end-of-defun, ruby-move-to-block, ruby-forward-sexp)
(ruby-backward-sexp, ruby-add-log-current-method)
(ruby-font-lock-syntactic-keywords, ruby-comment-beg-syntax)
(ruby-in-here-doc-p, ruby-mode): Fix typos in docstrings.
(ruby-deep-indent-paren): Doc fix.
(ruby-insert-encoding-magic-comment): Remove * from docstring.
(ruby-here-doc-find-end): Reflow docstring.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Thu, 11 Dec 2008 11:03:42 +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.