From: Simon Tournier <zimon.toutoune@gmail.com>
To: "John Kehayias" <john.kehayias@protonmail.com>,
"Marek Paśnikowski" <marekpasnikowski@protonmail.com>,
59855@debbugs.gnu.org
Subject: bug#59855: Emacs Debbugs reply (was Re: bug#59855: Guix Shell with FHS Feedback: lib/tls/x86_64/x86_64?)
Date: Thu, 05 Jan 2023 12:31:03 +0100 [thread overview]
Message-ID: <86a62x8bgo.fsf@gmail.com> (raw)
In-Reply-To: <87v8m2k7a8.fsf@protonmail.com>
Hi John,
On Fri, 23 Dec 2022 at 05:39, John Kehayias via Bug reports for GNU Guix <bug-guix@gnu.org> wrote:
> (resending as it seems debbugs in Emacs doesn't automatically add the
> bug number email in the To/CC list.)
Well, I think it is about Gnus and not Debbugs. There is bunch of
option to reply with Gnus. :-)
9 candidates:
gnus-summary-reply
gnus-summary-wide-reply
gnus-summary-very-wide-reply
gnus-summary-reply-with-original
gnus-summary-reply-broken-reply-to
gnus-summary-wide-reply-with-original
gnus-summary-reply-to-list-with-original
gnus-summary-very-wide-reply-with-original
gnus-summary-reply-broken-reply-to-with-original
Personally, I have this config (the only Gnus keybinding I use ;-))
(define-key gnus-summary-mode-map "R" 'gnus-summary-wide-reply-with-original)
(define-key gnus-article-mode-map "R" 'gnus-summary-wide-reply-with-original)
which is consistent with Emacs Notmuch key binding.
Hope that helps,
simon
next prev parent reply other threads:[~2023-01-05 12:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 9:07 bug#59855: Guix Shell with FHS Feedback: lib/tls/x86_64/x86_64? Marek Paśnikowski via Bug reports for GNU Guix
2022-12-23 5:39 ` John Kehayias via Bug reports for GNU Guix
2023-01-05 11:31 ` Simon Tournier [this message]
2023-01-19 21:38 ` bug#59855: Emacs Debbugs reply (was Re: bug#59855: Guix Shell with FHS Feedback: lib/tls/x86_64/x86_64?) John Kehayias via Bug reports for GNU Guix
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a62x8bgo.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=59855@debbugs.gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=marekpasnikowski@protonmail.com \
/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://git.savannah.gnu.org/cgit/guix.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).