unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jason Schroeder" <shrode@subnature.com>
Subject: todo-mode.el comment patch
Date: Sat, 30 Mar 2002 22:09:56 -0800 (PST)	[thread overview]
Message-ID: <20020330220957.952.c001-h014.c001.wm@mail.subnature.com.criticalpath.net> (raw)

Hi.

lisp/calendar/todo-mode.el is missing some relevant comments.  The next new
user can avoid
reading the elisp code if the following was included in the comments.

This is an anonymous donation for all I care.

Jason Schroeder

--- todo-mode.el~	Tue Nov 13 04:12:45 2001
+++ todo-mode.el	Sun Mar 31 06:03:58 2002
@@ -69,6 +69,28 @@
 ;;      in order to initialise the file, but it is not necessary
 ;;      afterwards.
 ;;
+;;      TODO is designed to be used in conjunction with diary mode. This
+;;      indicates the purpose of the pattern "*/*" (aka todo-prefix below)
+;;      in the TODO files.  The following are diary specific
initializations
+;;      used to expose the TODO/diary functionality.
+;;
+;;      In the diary-file, you add the line:
+;;          #include "~/.todo-do"
+;;      (The file name is the same as todo-file-do.)
+;;
+;;      Also, you add the following in order to cause the diary include
+;;      include feature to work.
+;;          (add-hook 'diary-display-hook 'fancy-diary-display)
+;;          (add-hook 'list-diary-entries-hook 'include-other-diary-files)
+;;
+;;      And, when using the diary mode in conjunction with the calendar
mode,
+;;      the first turns that feature on and the second controls whether the
+;;      todo items are indicated on the calendar.  I do not suggest the use
+;;      of the diary marking feature in conjunction with TODO.
+;;
+;;          (add-hook 'diary-hook 'appt-make-list)
+;;          (add-hook 'mark-diary-entries-hook 'mark-included-diary-files)
+;;
 ;;      As these commands are quite long to type, I would recommend
 ;;      the addition of two bindings to your to your global keymap.  I
 ;;      personally have the following in my initialisation file:

                 reply	other threads:[~2002-03-31  6:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020330220957.952.c001-h014.c001.wm@mail.subnature.com.criticalpath.net \
    --to=shrode@subnature.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).