Mercurial > emacs
view BUGS @ 26507:aabdfbf65c68
1999-11-19 Francesco Potorti` <F.Potorti@cnuce.cnr.it>
* etags.c (_GNU_SOURCE): Define only if undefined.
(get_scheme): Declaration deleted.
(main): error was called with an integer as second arg, instead of
a char pointer.
(canonicalize_filename): Bug removed.
1999-11-18 Dave Love <d.love@dl.ac.uk>
* etags.c (C_entries): Rename label `intoken', avoiding K&R
lossage from name clash with macro.
author | Francesco Potortì <pot@gnu.org> |
---|---|
date | Fri, 19 Nov 1999 12:46:32 +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,"