annotate BUGS @ 93937:dfe13eac745b

* minibuffer.el (minibuffer): Move group from cus-edit.el. (completion-auto-help): Move from C code. (minibuffer--maybe-completion-help): Remove. (minibuffer--bitset): New function. (minibuffer--do-completion): Rename from minibuffer-do-completion. Renumber a bit. Really complete on string *before* point. Add argument used for word-completion. Join trailing / in completion with following text, as done in minibuffer-complete-word. Handle new value `lazy' for completion-auto-help. (minibuffer-try-word-completion): New function extracted from minibuffer-complete-word. (minibuffer-complete-word): Use minibuffer--do-completion. (minibuffer--insert-strings): Rename from minibuffer-complete-insert-strings. (exit-minibuffer): Fix typo. * cus-edit.el (minibuffer): Move group to minibuffer.el. * cus-start.el: Remove completion-auto-help. * minibuf.c (Vcompletion_auto_help): Move to minibuffer.el. (syms_of_minibuf): Remove its initialization.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Wed, 09 Apr 2008 19:33:56 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
25856
Dave Love <fx@gnu.org>
parents:
diff changeset
1 If you think you may have found a bug in GNU Emacs, please
Dave Love <fx@gnu.org>
parents:
diff changeset
2 read the Bugs section of the Emacs manual for advice on
Dave Love <fx@gnu.org>
parents:
diff changeset
3 (1) how to tell when to report a bug, and
Dave Love <fx@gnu.org>
parents:
diff changeset
4 (2) how to write a useful bug report and what information
Dave Love <fx@gnu.org>
parents:
diff changeset
5 it needs to have.
Dave Love <fx@gnu.org>
parents:
diff changeset
6
Dave Love <fx@gnu.org>
parents:
diff changeset
7 There are three ways to read the Bugs section.
Dave Love <fx@gnu.org>
parents:
diff changeset
8
Dave Love <fx@gnu.org>
parents:
diff changeset
9 (1) In a printed copy of the Emacs manual.
Dave Love <fx@gnu.org>
parents:
diff changeset
10 You can order one from the Free Software Foundation;
Dave Love <fx@gnu.org>
parents:
diff changeset
11 see the file etc/ORDERS. But if you don't have a copy on
Dave Love <fx@gnu.org>
parents:
diff changeset
12 hand and you think you have found a bug, you shouldn't wait
Dave Love <fx@gnu.org>
parents:
diff changeset
13 to get a printed manual; you should read the section right away
Dave Love <fx@gnu.org>
parents:
diff changeset
14 as described below.
Dave Love <fx@gnu.org>
parents:
diff changeset
15
Dave Love <fx@gnu.org>
parents:
diff changeset
16 (2) With Info. Start Emacs, do C-h i to enter Info,
Dave Love <fx@gnu.org>
parents:
diff changeset
17 then m Emacs RET to get to the Emacs manual, then m Bugs RET
Dave Love <fx@gnu.org>
parents:
diff changeset
18 to get to the section on bugs. Or use standalone Info in
Dave Love <fx@gnu.org>
parents:
diff changeset
19 a like manner. (Standalone Info is part of the Texinfo distribution,
Dave Love <fx@gnu.org>
parents:
diff changeset
20 not part of the Emacs distribution.)
Dave Love <fx@gnu.org>
parents:
diff changeset
21
Dave Love <fx@gnu.org>
parents:
diff changeset
22 (3) By hand. Do
Dave Love <fx@gnu.org>
parents:
diff changeset
23 cat info/emacs* | more "+/^File: emacs, Node: Bugs,"
Dave Love <fx@gnu.org>
parents:
diff changeset
24
55212
8ce686bd7f4f Update key binding for viewing PROBLEMS.
Richard M. Stallman <rms@gnu.org>
parents: 34822
diff changeset
25 Please first check the file etc/PROBLEMS (e.g. with C-h C-e in Emacs) to
34822
af68d12218d0 *** empty log message ***
Dave Love <fx@gnu.org>
parents: 25856
diff changeset
26 make sure it isn't a known issue.