view BUGS @ 69748:e44b79389d65

(ido-unc-hosts-cache): New defvar. (ido-unc-hosts): If value of defcustom is a function, call it to get list of UNC hosts. Add function-item choices to specify ido-unc-hosts-net-view or user function. (ido-ignore-unc-host-regexps): New defcustom. (ido-unc-hosts-net-view, ido-unc-hosts): New functions. (ido-is-unc-root, ido-is-unc-host, ido-file-name-all-completions) (ido-exhibit): Call ido-unc-hosts to get list of UNC hosts.
author Kim F. Storm <storm@cua.dk>
date Fri, 31 Mar 2006 23:47:02 +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.