From: Kai Grossjohann <grossjohann@amaunet.cs.uni-dortmund.de>
Cc: ding@gnus.org
Subject: Re: fortune on the end of .signature
Date: 09 Sep 1998 09:44:38 +0200 [thread overview]
Message-ID: <vafhfyhhgrd.fsf@ramses.cs.uni-dortmund.de> (raw)
In-Reply-To: Phil Humpherys's message of "08 Sep 1998 22:59:55 -0600"
>>>>> On 08 Sep 1998, Phil Humpherys said:
Phil> What's the lisp that I would use to have gnus append an
Phil> invocation of the fortune program on the end of each article
Phil> or email I send out?
Untested:
(defun my-message-do-fortune ()
(save-excursion
(message-goto-signature)
(forward-line 3) ; change this according to length of sig!
(call-process "/usr/bin/fortune" nil t nil)))
(add-hook 'message-setup-hook 'my-message-do-fortune)
kai
--
OOP: object oriented programming; OOPS: object oriented mistakes
next prev parent reply other threads:[~1998-09-09 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-09 4:59 Phil Humpherys
1998-09-09 5:42 ` Kees de Bruin
1998-09-09 7:44 ` Kai Grossjohann [this message]
1998-09-09 12:44 ` Vladimir Volovich
1998-09-09 16:05 ` Manoj Srivastava
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=vafhfyhhgrd.fsf@ramses.cs.uni-dortmund.de \
--to=grossjohann@amaunet.cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).