From: Tomi Ollila <tomi.ollila@iki.fi>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] emacs: add function to resend message to new recipients
Date: Sun, 30 Aug 2015 17:58:48 +0300 [thread overview]
Message-ID: <m2a8t8257b.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <87vbbxrl3g.fsf@maritornes.cs.unb.ca>
On Sun, Aug 30 2015, David Bremner <david@tethera.net> wrote:
> Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> The new function notmuch-show-message-resend re-sends
>> message to new recipients using #'message-resend.
>>
>> Recipients are read from minibuffer as a comma-separated
>> string (with some keyboard support including tab completion).
>>
>
> I couldn't get the tab completion to work, at least if I go
>
> M-x notmuch-show-resend-message
>
> nor when evaluating (notmuch-address-from-minibuffer "foo:")
>
> Do I need to bind a key to test this?
Nope. both of the above should work -- and worked for me just now
(this is how I tested just now:
emacs -q -L $PWD/emacs -l emacs/notmuch.el -f notmuch --eval '(progn (setq notmuch-address-command "nottoomuch-addresses.sh") (notmuch-address-message-insinuate))'
)
>> I remember that Emacs VM might have had 'b' bound to this functionality
>> but I cannot be sure. A few weeks ago I looked gnus, rmail & mh-e to
>> figure out whether 'b' would have been bound to similar functionality
>> there but I cannot find it...
>
> mutt uses 'b'. AFAICT, gnus uses some sequence ending in b to resend
> bounced messages (i.e. from mailer-daemon).
>
> quoting the manual:
>
> S D b
>
> If you have sent a mail, but the mail was bounced back to you for
> some reason (wrong address, transient failure), you can use this
> command to resend that bounced mail
> (gnus-summary-resend-bounced-mail). [...]
>
> S D r
>
> Not to be confused with the previous command,
> gnus-summary-resend-message will prompt you for an address to send
> the current message off to, and then send it to that place. [...]
>
> Be that as it may, we already use 'r' for reply, and I'm not sure we
> want to go (more) in the way of multi-letter sequences.
I agree that we don't want to to multi-letter sequences (early). I
personally would be fine w/ 'b'...
Tomi
next prev parent reply other threads:[~2015-08-30 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 20:07 [PATCH 1/2] emacs: add defsubst notmuch-address--message-insinuated Tomi Ollila
2015-08-26 20:07 ` [PATCH 2/2] emacs: add function to resend message to new recipients Tomi Ollila
2015-08-30 12:56 ` David Bremner
2015-08-30 14:58 ` Tomi Ollila [this message]
2015-08-31 1:42 ` David Bremner
2015-08-31 19:01 ` Tomi Ollila
2015-08-31 23:11 ` David Bremner
2015-08-30 12:28 ` [PATCH 1/2] emacs: add defsubst notmuch-address--message-insinuated David Bremner
2015-08-30 15:02 ` Tomi Ollila
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2a8t8257b.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).