From: Boruch Baum <boruch_baum@gmx.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: ~Make emacs friendlier: package documentation [POC CODE INCLUDED]
Date: Sun, 18 Oct 2020 10:43:45 -0400 [thread overview]
Message-ID: <20201018144345.wgrbsivvzuuohbj5@E15-2016.optimum.net> (raw)
In-Reply-To: <jwvsgabn0lg.fsf-monnier+emacs@gnu.org>
On 2020-10-18 09:11, Stefan Monnier wrote:
> > 1) I share the sentiment about consolidating the help/describe commands,
> > and have no objection to the feature being accessed via a link in
> > describe-package (ie. no direct dedicated keybinding).
>
> IIUC your pack-doc provides a superset of what `C-h P` provides.
No, the only intersection is the 'commentary' text taken from the elisp
file. describe-package presents a unique heading summary; for example:
#+BEGIN_QUOTE
yasnippet is a dependency package.
Status: Installed in ‘yasnippet-20200524.2215/’ (unsigned).
Version: 20200524.2215
Commit: d3d6d70b1cd4818d271752468e0fdb0788db750d
Summary: Yet another snippet extension for Emacs
Requires: cl-lib-0.5
Homepage: http://github.com/joaotavora/yasnippet
Keywords: [convenience] [emulation]
Other versions: 20200604.246 (melpa), 0.14.0 (gnu), 0.6.1 (marmalade).
#+END_QUOTE
> So what would be the downside(s) of replacing `C-h P` with your packdoc?
I have no objection, but I do like the heading summary that
describe-package presents, and think it would be a shame to lose it.
> IOW what would be the advantage of adding a link in `C-h P` to your
> system, instead of just replacing `C-h P` with your system?
IMO: Just losing the heading summary, but that code can be integrated so
that nothing would be lost.
Playing devil's advocate: I'm not any kind of UX psychologist, but if
there is someone like that on the list, they could speak to the notion
of it maybe being a situation of presenting 'too much information' for a
user expecting the prior behavior or for a user just wanting the most
basic package description or for a user unfamiliar with org-mode.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-10-18 14:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:09 ~Make emacs friendlier: package documentation [POC CODE INCLUDED] Boruch Baum
2020-10-15 19:24 ` Eli Zaretskii
2020-10-15 19:41 ` Boruch Baum
2020-10-16 6:39 ` Eli Zaretskii
2020-10-16 7:34 ` Boruch Baum
2020-10-16 10:20 ` Eli Zaretskii
2020-10-18 5:58 ` Boruch Baum
2020-10-18 14:53 ` Eli Zaretskii
2020-10-18 15:05 ` Boruch Baum
2020-10-18 15:12 ` Eli Zaretskii
2020-10-18 15:28 ` Boruch Baum
2020-10-18 16:00 ` Eli Zaretskii
2020-10-18 16:29 ` Boruch Baum
2020-10-18 17:05 ` Eli Zaretskii
2020-10-18 13:11 ` Stefan Monnier
2020-10-18 14:43 ` Boruch Baum [this message]
2020-10-18 15:50 ` Stefan Kangas
2020-10-18 16:20 ` Boruch Baum
2020-10-18 17:13 ` Stefan Kangas
2020-10-18 20:40 ` Kévin Le Gouguec
2020-10-19 2:55 ` Boruch Baum
2020-10-21 5:52 ` Kévin Le Gouguec
2020-10-21 6:00 ` Boruch Baum
2020-10-21 22:31 ` Stefan Monnier
2020-10-18 15:58 ` Boruch Baum
2020-10-18 20:18 ` Stefan Monnier
2020-10-19 2:24 ` Eli Zaretskii
2020-10-19 2:59 ` Boruch Baum
2020-10-19 3:16 ` Stefan Monnier
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:51 ` Boruch Baum
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=20201018144345.wgrbsivvzuuohbj5@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).