view BUGS @ 39150:a56fcade3c7e

(Help, mainline code): Add new option -L FILE. (Copyright): Update year. (LANG, LANGUAGE, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, LC_NUMERIC, LC_TIME): New shell vars, to make sure we live in the C locale. (mainline code): Handle nonstandard -u option differently, by transforming it to standard form. Check for "Working file: ", not "Working file:". Allow file names with spaces. (SOH, rlogfile): New shell vars. (rlogout): Remove. Its old functionality is mostly migrated to rlogfile. Append ';;' to the last arm of every case statement, for portability to ancient broken BSD shells. (logins): Fix bug; was not being computed at all, lowering performance. (pository): New var. This fixes some bugs where repositories are remote, or have trailing slashes. (authors): $llogout is never an empty shell var, so don't worry about that possibility. (printlogline, mainline code): Fix bug with SOH's being put into the output.
author Paul Eggert <eggert@twinsun.com>
date Wed, 05 Sep 2001 23:07:46 +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.