view BUGS @ 108234:06c34f190db1

Remove POSIX_SIGNALS. * s/usg5-4.h (POSIX_SIGNALS): * s/netbsd.h (POSIX_SIGNALS): * s/msdos.h (POSIX_SIGNALS): * s/ms-w32.h (POSIX_SIGNALS): * s/hpux11.h (POSIX_SIGNALS): * s/gnu.h (POSIX_SIGNALS): * s/gnu-linux.h (POSIX_SIGNALS): * s/freebsd.h (POSIX_SIGNALS): * s/darwin.h (POSIX_SIGNALS): * s/cygwin.h (POSIX_SIGNALS): * s/aix4-2.h (POSIX_SIGNALS): Remove definition. * s/unixware.h: * s/sol2-6.h: Remove comments on POSIX_SIGNALS. * process.c (create_process): * syssignal.h: * sysdep.c (wait_for_termination, init_signals): * process.c (create_process): * msdos.c: POSIX_SIGNALS is always defined on all platforms, remove all code that assumes the contrary.
author Dan Nicolaescu <dann@ics.uci.edu>
date Mon, 03 May 2010 21:00:10 -0700
parents fb8bf24d2eb9
children ac52af4a044c
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-p in Emacs) to
make sure it isn't a known issue.