From: "Y. E." <yugenekr@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 40457@debbugs.gnu.org
Subject: bug#40457: 26.3; A little Help from `list-packages'?
Date: Thu, 24 Jun 2021 13:59:24 +0300 [thread overview]
Message-ID: <CAFCpf7A96t2+FYv31tP8U_B67AZid74Wq26reDAfWaHcQJmDKw@mail.gmail.com> (raw)
In-Reply-To: <87eed4y1am.fsf@gnus.org>
> (emacs) `Package Menu' helps. But the buffer itself (and its menu and
> help commands) should provide better help.
So maybe link from the package-mode *Help* to (emacs) `Package Menu'?
(That's what I first thought Tomas meant.)
> Most of the rest of the bug report is about whether the batch-oriented
> command set of package.el is appropriate. I think marking and then
> `x'-executing packages is a pretty odd interface myself -- I don't think
> the user commonly works in that batch-oriented way, so having this be a
> two step process is pretty weird.
For me, it felt weird only before reading *Help* of the package-mode.
After that, it felt quite in accordance with the rest of Emacs behavior.
[But that depends of course on whether a user has already met
the e*x*ecute behavior and without considering inconsistencies
in Emacs behavior when e*x*ecuting on not-marked lines.]
I think with new keystrokes there's a risk to confuse (especially a new user)
even more: for example, using I (uppercase-i) and D per one package
install/delete would make already inconsistent U even more inconsistent.
Maybe also change `package-menu-quick-help' output:
it could be improved by mentioning *marking*, not only the action.
next prev parent reply other threads:[~2021-06-24 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 21:18 bug#40457: 26.3; A little Help from `list-packages'? Drew Adams
2020-04-06 8:32 ` Tomas Nordin
2020-04-06 15:35 ` Drew Adams
2021-06-14 14:21 ` Lars Ingebrigtsen
2021-06-24 10:59 ` Y. E. [this message]
2021-06-24 15:02 ` Lars Ingebrigtsen
2021-06-25 12:17 ` Y. E.
2021-06-25 14:07 ` Lars Ingebrigtsen
2022-05-07 12:31 ` Lars Ingebrigtsen
2022-05-07 16:04 ` Drew Adams
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=CAFCpf7A96t2+FYv31tP8U_B67AZid74Wq26reDAfWaHcQJmDKw@mail.gmail.com \
--to=yugenekr@gmail.com \
--cc=40457@debbugs.gnu.org \
--cc=larsi@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.
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).