From: Michael Albinus <michael.albinus@gmx.de>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
noam postavsky <npostavs@gmail.com>,
34976@debbugs.gnu.org
Subject: bug#34976: [debbugs.el] debbugs-read-emacs-bug-with-gnus sets user options
Date: Mon, 25 Mar 2019 19:25:54 +0100 [thread overview]
Message-ID: <87ef6uq099.fsf@gmx.de> (raw)
In-Reply-To: <8736narfc0.fsf@tcd.ie> (Basil L. Contovounesios's message of "Mon, 25 Mar 2019 18:14:55 +0000")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
Hi Basil,
> Sorry if I'm missing something obvious, but how would setting this new
> debbugs user option be different from setting the existing Gnus user
> options? In other words, why can't users who want a Lars-esque workflow
> (Larsflow?) just set the gnus-* user options themselves? Wouldn't the
> proposed debbugs user option be redundant?
IIUC, Lars doesn't set these variables in his .emacs permanently. He
needs them *only* in case of debbug-gnu, when a gnus-ephemeral group is
created. The proposed variable does this for him.
Otherwise, he would need to wrap the debbugs-gnu commands by own ones.
> Thanks,
Best regards, Michael.
next prev parent reply other threads:[~2019-03-25 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-24 15:32 bug#34976: [debbugs.el] debbugs-read-emacs-bug-with-gnus sets user options Basil L. Contovounesios
2019-03-25 16:45 ` Michael Albinus
2019-03-25 17:40 ` Lars Ingebrigtsen
2019-03-25 17:46 ` Michael Albinus
2019-03-25 17:48 ` Lars Ingebrigtsen
2019-03-25 18:14 ` Basil L. Contovounesios
2019-03-25 18:25 ` Michael Albinus [this message]
2019-03-25 18:41 ` Basil L. Contovounesios
2019-03-25 18:55 ` Michael Albinus
2019-03-26 15:56 ` Michael Albinus
2019-03-26 16:16 ` Lars Ingebrigtsen
2019-03-26 16:21 ` Michael Albinus
2019-03-27 3:56 ` Basil L. Contovounesios
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ef6uq099.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=34976@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.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/emacs.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).