From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: ding@gnus.org
Subject: Re: [feature request] `message-send-rename-function' hooks
Date: Wed, 21 Sep 2011 19:50:56 +0200 [thread overview]
Message-ID: <m3zkhx6ayn.fsf@stories.gnus.org> (raw)
In-Reply-To: <m2ehzhqpir.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Thu, 15 Sep 2011 20:50:20 -0400")
Dave Abrahams <dave@boostpro.com> writes:
> For *my* purposes, it would be sufficient to break out the code from
> `message-do-send-housekeeping' and create what is essentially the
> default `message-send-rename-function'. I could then have my rename
> function call that and then adjust the buffer name again. Others might
> want more control, of course.
I've now separated the code out into
`message-default-send-rename-function'.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-09-21 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 0:50 Dave Abrahams
2011-09-21 17:50 ` Lars Magne Ingebrigtsen [this message]
2011-09-21 18:19 ` Dave Abrahams
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=m3zkhx6ayn.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=dave@boostpro.com \
--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).