view BUGS @ 44368:ceb605d3c4dd

(cal-tex-hook, cal-tex-year-hook, cal-tex-month-hook) (cal-tex-week-hook, cal-tex-daily-hook): Add doc strings. (cal-tex-latexify-list): Fix doc string. (cal-tex-insert-day-names): LaTeXify day names. (cal-tex-cursor-week-iso, cal-tex-week-hours, cal-tex-weekly4-box) (cal-tex-cursor-filofax-2week, cal-tex-cursor-filofax-week) (cal-tex-daily-page, cal-tex-mini-calendar): LaTeXify day names. Change all instances (interactive "P") to (interactive "p"). (cal-tex-cursor-month): Add hfill and newline at end of month that ended on Saturday. (cal-tex-preamble): Change to LaTeX2e. (cal-tex-cursor-filofax-year): Don't use default month names in LaTeX macros in case user changes them. (cal-tex-month-name): New function. Used throughout in case user has done something funny with month names.
author Richard M. Stallman <rms@gnu.org>
date Wed, 03 Apr 2002 14:35:33 +0000
parents af68d12218d0
children 8ce686bd7f4f
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 P in Emacs) to
make sure it isn't a known issue.