view BUGS @ 58922:3e3c16ff820c

(find-file-other-window, find-file-other-frame): Add the first buffer to the returned value to return the complete list of all visited buffers. (find-file-read-only, find-file-read-only-other-window) (find-file-read-only-other-frame): Use nil for `mustmatch' arg of `find-file-read-args'. Signal an error about non-existent file only if file name doesn't contain wildcards. Toggle read-only in all visited buffers. (find-alternate-file, find-alternate-file-other-window): Add optional arg `wildcards'. Doc fix. Set `wildcards' to t when called interactively. Pass arg `wildcards' to other functions. (find-file-noselect): Doc fix.

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.