From: Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de>
Cc: ding@ifi.uio.no
Subject: Re: Message feature requests and gnus elisp query
Date: 14 Oct 1996 09:14:41 +0200 [thread overview]
Message-ID: <vafhgnyqaou.fsf@ls6.informatik.uni-dortmund.de> (raw)
In-Reply-To: dubach1@husc.harvard.edu's message of 13 Oct 1996 19:42:11 -0400
>>>>> Joev Dubach writes:
Joev> (defun my-reply-mainly-mail-also-news ()
Joev> "Compose mail that can also be news, but which won't have a courtesy
Joev> message in the mail version."
Joev> (interactive)
Joev> (gnus-summary-reply)
Joev> (setq message-courtesy-message ""))
Would this work?
(defun my-reply-mainly-mail-also-news ()
(interactive)
(let ((message-courtesy-message ""))
(gnus-summary-reply)))
kai
--
Life is hard and then you die.
next prev parent reply other threads:[~1996-10-14 7:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-13 23:42 Joev Dubach
1996-10-14 7:14 ` Kai Grossjohann [this message]
1996-10-14 8:36 ` Joev Dubach
1996-10-14 20:23 ` Lars Magne Ingebrigtsen
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=vafhgnyqaou.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjohann@charly.informatik.uni-dortmund.de \
--cc=ding@ifi.uio.no \
/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).