annotate BUGS @ 92920:cb0aac9dd8a3

(calendar-mayan-haab-month-name-array) (calendar-mayan-tzolkin-names-array): Add doc strings. (calendar-mayan-long-count-from-absolute): Use a single let. (calendar-string-to-mayan-long-count): Simplify. (calendar-next-haab-date, calendar-previous-haab-date) (calendar-next-tzolkin-date, calendar-previous-tzolkin-date) (calendar-previous-calendar-round-date) (calendar-goto-mayan-long-count-date, calendar-mayan-date-string): Doc fix. (calendar-mayan-tzolkin-haab-on-or-before): Use zerop. (calendar-mayan-date-string, calendar-print-mayan-date) (calendar-read-mayan-haab-date, calendar-read-mayan-tzolkin-date) (calendar-mayan-long-count-common-era): Move definitions before use.

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-e in Emacs) to
make sure it isn't a known issue.