view BUGS @ 110712:9f132a615f50

Remove some unused ps-def definitions. * lisp/ps-def.el (leading-code-private-22, charset-bytes, charset-id) (charset-width, find-charset-region, chars-in-region, forward-point) (encode-coding-string, coding-system-p, ccl-execute-on-string) (define-ccl-program, multibyte-string-p, string-make-multibyte): Remove compatibility cruft (none of these are used by ps*.el).
author Glenn Morris <rgm@gnu.org>
date Sat, 02 Oct 2010 18:35:07 -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.