view BUGS @ 61560:a54fc673c31c

(org-agenda-date-prompt): Renamed from `org-agenda-date-today'. (org-evaluate-time-range): Insert at point instead of directly after time range. (org-first-headline-recenter, org-subtree-end-visible-p) (org-optimize-window-after-visibility-change): New functions (org-agenda-post-command-hook): Don't allow point at end of line, to make sure it always hits the text properties. (org-agenda-next-date-line, org-agenda-previous-date-line): New commands. (org-set-regexps-and-options): Category may contain white space. (org-agenda-get-deadlines, org-agenda-get-scheduled): Improved marker positions. (org-agenda-new-marker): Argument POS made optional. (org-agenda-get-timestamps): Deadlines which are done are listed in org-done-face now. (org-agenda-get-todos, org-agenda-get-timestamps) (org-agenda-get-deadlines, org-agenda-get-scheduled): set `undone-face' and `done-face' properties. (org-last-todo-state-is-todo): New variable. (org-todo): Set `org-last-todo-state-is-todo'. (org-agenda-todo): Change face according to `org-last-todo-state-is-todo'. And change other lines refering to the same entry. (org-calendar-goto-agenda): New command. (org-calendar-to-agenda-key): New option. (org-startup-folded): New allowed value `content'. (org-set-regexps-and-options): Accept new value `content' for `org-startup-folded'. (org-get-current-options): Handle new value `content' for `org-startup-folded'. (org-insert-todo-heading): New command. (org-mode): Insert first line "*-* mode: org-mode -*-" when called interactively in empty file and option `org-insert-mode-line-in-empty-file' has been set. (org-agenda-todo,org-agenda-priority): Modified to use `org-agenda-change-all-lines'. (org-warning-face): Changed color on dark background
author Carsten Dominik <dominik@science.uva.nl>
date Fri, 15 Apr 2005 06:49:56 +0000
parents 8ce686bd7f4f
children fb8bf24d2eb9
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-e in Emacs) to
make sure it isn't a known issue.