From: lawrence mitchell <wence@gmx.li>
Subject: Re: Diary functions
Date: Fri, 06 Sep 2002 13:17:55 +0100 [thread overview]
Message-ID: <wkk7lz9urw.fsf@ID-97657.usr.dfncis.de> (raw)
In-Reply-To: 87fzwn1g0i.fsf@smtp.blueyonder.co.uk
Keith O'Connell wrote:
> I have just taken to using the calendar/diary combination in emacs and
> am pleasently surprised that it is all I need and that the various
> solutions I have used up till now have been overkill! :-)
> However, I have hit a small snag. The local lug meets on the first
> Tursday of the month. How does one set a repeating entry for these
> regular, yet irregular types of events?
You probably want to read the section in the Emacs Lisp manual
entitled "Sexp Entries and the Fancy Diary Display", which points
in the direction of the function `diary-float'. An online
version of this manual is available at: <URL: http://www.gnu.org/
manual/elisp-manual-21-2.8/html_chapter/elisp_39.html#SEC675>.
--
lawrence mitchell <wence@gmx.li>
next prev parent reply other threads:[~2002-09-06 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-06 12:03 Diary functions Keith O'Connell
2002-09-06 12:17 ` lawrence mitchell [this message]
2002-09-06 12:37 ` Keith O'Connell
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=wkk7lz9urw.fsf@ID-97657.usr.dfncis.de \
--to=wence@gmx.li \
/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.
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).