Mercurial > emacs
view BUGS @ 67621:0d6832f365fb
(choose-completion): Use `buffer-substring-no-properties'
instead of `buffer-substring'.
(completion-common-substring): Doc fix.
(completion-setup-function): Use minibuffer-completion-contents
instead of minibuffer-contents. Don't set common-string-length
initially. Remove special handling of partial-completion-mode.
Move computation of completion-base-size into one cond. Call
completion-base-size-function in mainbuf. In computation of
completion-base-size for file name completion don't move point to
the end of the minibuffer. Move computation of common-string-length
into one cond. Start putting faces only when common-string-length>=0.
Add condition to put completions-common-part when common-string-length>0.
author | Juri Linkov <juri@jurta.org> |
---|---|
date | Fri, 16 Dec 2005 19:08:21 +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.