view BUGS @ 46801:3fafc6fca8a8

Version 2.0.9 released. (tramp-bug): Add wording about additional info to include in bug report. (tramp-find-shell): Set $PS1 for invocation of second shell (for tilde expansion). (tramp-find-shell): Shell prompt must match at end of buffer. Do this also for fallback shell prompt. (tramp-find-shell): More debugging output. (tramp-find-inline-encoding): When checking the decoding command, some commands fail when reading from /dev/null. So we pass a known string through the encoding command and pass that through the decoding command. So we know whether the decoding command can deal with some real input.
author Kai Großjohann <kgrossjo@eu.uu.net>
date Sun, 04 Aug 2002 11:41:38 +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.