Mercurial > emacs
view BUGS @ 53827:44d25617bd98
(Fminibufferp, Fread_from_minibuffer)
(Fread_minibuffer, Feval_minibuffer)
(Fread_string, Fread_no_blanks_input)
(Fcompleting_read): Doc fixes.
(syms_of_minibuf): Doc fixes for minibuffer-completion-table and
completion-regexp-list. Define Qcase_fold_search and staticpro it.
(read_minibuf): Fix initial comment.
(Ftry_completion, Fall_completions, Ftest_completion): Bind
case-fold-serach to the value of completion-ignore-case when
checking completion-regexp-list.
(Fdisplay_completion_list): Make it handle arguments that are
symbols. Doc fix.
author | Luc Teirlinck <teirllm@auburn.edu> |
---|---|
date | Fri, 06 Feb 2004 04:49:55 +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.