Mercurial > emacs
view BUGS @ 110895:b803c876a460
Fix building manuals on MS-Windows using emacsver.texi.
misc/makefile.w32-in (emacsdir): New variable.
($(infodir)/efaq, faq.dvi): Depend on emacsver.texi.
(ENVADD, $(infodir)/efaq): Add -I$(emacsdir).
emacs/makefile.w32-in (EMACSSOURCES): Add emacsver.texi.
lispref/makefile.w32-in (emacsdir): New variable.
(srcs): Add emacsver.texi.
($(infodir)/elisp, elisp.dvi): Add -I$(emacsdir).
author | Eli Zaretskii <eliz@gnu.org> |
---|---|
date | Sat, 09 Oct 2010 23:38:04 +0200 |
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.