view BUGS @ 31106:ad1ae9eb641a

(GetCachedVolumeInformation): Use xmalloc, xfree and xstrdup. (add_volume_info): Use xstrdup. (init_environment): Call _access. (check_windows_init_file): Call _close. (init_user_info): Call _putenv. (init_environment): Call _putenv and _strdup. (init_ntproc): Reset volume info cache on startup. (unc_volume_file_attributes): (open_unc_volume): Make arg const. (gettimeofday): Use struct timeb, not struct _timeb. (map_w32_filename, read_unc_volume): Fix compile warning. (sys_strerror): Use sys_nerr instead of _sys_nerr. Use sys_errlist instead of _sys_errlist. (get_emacs_configuration_options): New function.
author Andrew Innes <andrewi@gnu.org>
date Tue, 22 Aug 2000 22:49:27 +0000
parents 354e0c45cedf
children af68d12218d0
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,"