view BUGS @ 92159:9ed7610349d3

* configure.in: Remove references to obsolete variables and systems. * configure: Regenerate. * Makefile.in (NO_SHORTNAMES): * emacsclient.c (NO_SHORTNAMES): * fakemail.c (NO_SHORTNAMES): * make-docfile.c (NO_SHORTNAMES): * movemail.c (NO_SHORTNAMES): * pop.c (NO_SHORTNAMES): Remove references to obsolete variable. * config.nt (SHORTNAMES): Remove reference to obsolete variable. * s/vms4-0.h: * s/vms4-2.h: * s/vms4-4.h: * s/vms5-5.h: Remove, unused. * s/irix5-2.h: * s/irix6-0.h: * s/riscos5.h: * s/mach-bsd4-3.h: * m/mips4.h: Remove files for obsolete systems * Makefile.in: * filelock.c: * unexmips.c: * m/hp9000s300.h: * m/iris4d.h: * s/aix3-1.h: * s/hpux.h: * s/msdos.h: * s/usg5-0.h: * s/usg5-2-2.h: * s/usg5-2.h: * s/usg5-3.h: Remove references to obsolete variables. * s/irix5-0.h: Remove, move all the contents ... * s/irix6-5.h: ... here. Simplify. * config.in: Regenerate.

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.