From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bzg@gnu.org, stefankangas@gmail.com, 41373@debbugs.gnu.org,
rms@gnu.org, dgutov@yandex.ru
Subject: bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages
Date: Mon, 01 Jun 2020 12:25:11 -0700 [thread overview]
Message-ID: <87mu5ma8rs.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <83k10qeih8.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 01 Jun 2020 21:41:55 +0300")
On 06/01/20 21:41 PM, Eli Zaretskii wrote:
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Mon, 01 Jun 2020 11:29:14 -0700
>> Cc: 41373@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
>> Richard Stallman <rms@gnu.org>, dgutov@yandex.ru
>>
>> + (interactive (list
>> + (read-string "Bug Subject: ")
>> + (completing-read
>> + "Package: "
>> + (progn
>> + (package-initialize)
>> + package-alist)
>> + nil nil)))
>
> Does this mean reporting a bug will initialize all the packages that
> are installed? Will it also access the network and check for
> upgrades?
I don't believe so, no. But we should probably call `package-initialize'
with the NO-ACTIVATE argument, which will skip loading autoloads and
some other stuff. Or, for minimum invasiveness, just skip everything if
`package-alist' is nil.
> I'm not sure I understand the need to produce a potentially huge list
> of completion candidates, when it isn't even clear that the bug is
> about some add-on package. Can we be smarter about this?
Right, this is the part of the suggestion with the biggest question
marks. I can imagine the prompt would get annoying for frequent
contributors who are mostly filing bugs against emacs itself.
The only thing I can think of is providing a separate command,
`report-emacs-package-bug', that is a thin wrapper around
`report-emacs-bug'. That could live in package.el.
Actually, maybe that's the way to go?
next prev parent reply other threads:[~2020-06-01 19:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:14 bug#41373: GNU ELPA: Add "reporting bugs" to individual package pages Stefan Kangas
2020-05-18 18:04 ` Glenn Morris
2020-05-18 18:07 ` Eli Zaretskii
2020-05-19 0:20 ` Stefan Kangas
2020-05-18 18:12 ` Dmitry Gutov
2020-05-19 0:15 ` Stefan Kangas
2020-05-20 3:54 ` Richard Stallman
2020-05-20 5:30 ` Eric Abrahamsen
2020-05-25 9:04 ` Bastien
2020-05-25 15:39 ` Eric Abrahamsen
2020-05-25 17:09 ` Glenn Morris
2020-05-25 17:49 ` Eric Abrahamsen
2020-06-01 6:32 ` Bastien
2020-06-01 18:29 ` Eric Abrahamsen
2020-06-01 18:41 ` Eli Zaretskii
2020-06-01 19:25 ` Eric Abrahamsen [this message]
2020-06-01 19:38 ` Eli Zaretskii
2020-06-01 20:06 ` Eric Abrahamsen
2020-06-01 19:52 ` Glenn Morris
2020-06-01 20:31 ` Eric Abrahamsen
2020-05-25 11:51 ` Dmitry Gutov
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=87mu5ma8rs.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=41373@debbugs.gnu.org \
--cc=bzg@gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=rms@gnu.org \
--cc=stefankangas@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).