Gnus development mailing list
 help / color / mirror / Atom feed
From: Jody Klymak <jklymak@OCE.ORST.EDU>
Subject: Re: [ANNOUNCE] NNDiary, a diary backend for Gnus.
Date: Tue, 04 Sep 2001 08:15:43 -0700	[thread overview]
Message-ID: <66azf0m8.fsf@oce.orst.edu> (raw)
In-Reply-To: <muxpu989tbb.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Tue, 04 Sep 2001 11:06:22 +0200")

Didier Verna <didier@lrde.epita.fr> writes:

> Jody Klymak <jklymak@OCE.ORST.EDU> wrote:
>
>> It would also be nice if I could be in an arbitrary group and forward
>> messages to myself which add the X-Diary-* headers.  I can do this now
>> manually.  Any lisp hints on how to do it semi-automatically?
>
>         There's an entry in my gnus-diary todo list for composing fresh
> messages and prompting for the schedule. What you're asking makes me think
> we'd need to extract the schedule prompting part, and use it in the different
> message composing/forwarding/replying functions.

For now, I've defined the following which can be defined when I
compose (or more often forward) a message to myself:

Cheers,  Jody

(defun gnus-diary-add-header ()
  "Add nndiary compatible headers to the current buffer"   
  (interactive "*")
; Add an nndiary compatible header to a message
  (save-excursion
    (save-restriction
      (goto-char (point-min))
      (cond ((re-search-forward "^Subject: " nil t)
	     (goto-line (+ 1 (line-number)))
	     (let* ((heads nndiary-headers))
	       (while heads
		 (setq head (car heads))
		 (setq heads (cdr heads))
		 (insert (format "X-Diary-%s: *\n" (car head))))))
             (t (message "Not a mail message")))
      )))

-- 
Jody M. Klymak               mailto:jklymak@oce.orst.edu
College of Oceanic and Atmospheric Sicences
Oregon State University, Corvallis, OR, 97331  



  parent reply	other threads:[~2001-09-04 15:15 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-08 16:12 Didier Verna
2001-08-09  1:15 ` Colin Walters
2001-09-04  9:06   ` Didier Verna
2001-08-09  7:20 ` Jody Klymak
2001-08-09 11:14   ` Kai Großjohann
2001-08-09 15:14     ` Jody Klymak
2001-09-04  9:06   ` Didier Verna
2001-08-09 18:51 ` Jody Klymak
2001-08-10 19:10   ` Dan Nicolaescu
2001-08-10 19:14     ` Karl Kleinpaste
2001-08-10 21:07       ` Dan Nicolaescu
2001-08-10 21:49       ` Kai Großjohann
2001-08-10 22:12       ` Kai Großjohann
2001-08-10 22:25         ` Jody Klymak
2001-08-10 22:31           ` Jody Klymak
2001-08-11  0:04           ` Kai Großjohann
2001-08-11  0:27             ` Jody Klymak
2001-08-11 12:13               ` Kai Großjohann
2001-08-11 18:10                 ` Jody Klymak
2001-08-11 20:04                   ` Jody Klymak
2001-08-11 20:54                     ` Kai Großjohann
2001-09-04  8:13                       ` Didier Verna
2001-09-04 12:29                         ` Kai Großjohann
2001-09-04 15:49                           ` Paul Jarc
2001-09-04  8:09                   ` Didier Verna
2001-08-11 18:51                 ` Amos Gouaux
2001-09-04  8:03               ` Didier Verna
2001-08-11 18:50             ` Amos Gouaux
2001-08-11 20:52               ` Kai Großjohann
2001-08-10 22:50         ` Dan Nicolaescu
2001-08-13 18:29         ` Dan Nicolaescu
2001-09-04  9:06     ` Didier Verna
2001-09-04  9:06   ` Didier Verna
2001-09-04 12:25     ` Kai Großjohann
2001-09-04 15:15     ` Jody Klymak [this message]
2001-09-04 16:37       ` Kai Großjohann
2001-08-24 19:55 ` [ANNOUNCE] NNDiary to diary Jody Klymak

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

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

  git send-email \
    --in-reply-to=66azf0m8.fsf@oce.orst.edu \
    --to=jklymak@oce.orst.edu \
    /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 NNTP newsgroup(s).