Mercurial > emacs
view BUGS @ 27163:ea8740d15178
PostScript code now is in separate files, doc fix.
(ps-print-version): New version number (5.0.3).
(ps-header-lines, ps-left-header, ps-right-header): No more buffer
local.
(ps-spool-config): Initialization fix.
(ps-print-prologue-1, ps-print-prologue-2, ps-print-duplex-feature):
PostScript code moved to separated file.
(ps-background-image): Little code reformating.
(ps-begin-file, ps-begin-job): Fix code.
(ps-postscript-code-directory, ps-mark-code-directory): New
vars.
(ps-prologue-file): New fun.
author | Kenichi Handa <handa@m17n.org> |
---|---|
date | Wed, 05 Jan 2000 08:11:30 +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,"