From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: laszlomail@protonmail.com, emacs-devel@gnu.org
Subject: Re: Would you say this information window is well designed?
Date: Mon, 22 Feb 2021 23:49:43 +0200 [thread overview]
Message-ID: <84e3f5ab-436e-c0ea-39f1-2466f3227910@yandex.ru> (raw)
In-Reply-To: <83o8gbvr4m.fsf@gnu.org>
On 22.02.2021 21:28, Eli Zaretskii wrote:
>> The only extra info on the screenshot are the "View in manual" button
>> (which I would imagine you find appealing, given that it will lead more
>> users to read the manual) and the "References" section, which is not
>> essential, IMHO. The rest are mostly presentation.
>
> I _was_ talking about those two additions. (Though we don't see all
> of the buffer, only its top, so more surprises could be below.)
Yes, there are more. But I thought we were only discussing the
screenshot. To be clear, I'm not advocating for the additions of any of
those that would slow down the rendering of the Help buffer.
>> Though the "key bindings" section is interesting in that is also shows
>> the keymap where each bindings resides. This would have saved me some
>> extra debugging efforts in the past.
>
> Each one of these could be useful, but not all of them together, and
> not every time. It's too much. But as an opt-in feature, why not?
It will be a missed opportunity to teach some new users that they
can/should use the manual for more in-depth explanations.
Or that Emacs actually knows more about the function and its symbol.
Anyway, I'll stop here. If you don't think we should push for manual's
higher visibility, I certainly don't.
next prev parent reply other threads:[~2021-02-22 21:49 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 18:37 Would you say this information window is well designed? Peter Dean
2021-02-22 18:48 ` Eli Zaretskii
2021-02-22 19:23 ` Dmitry Gutov
2021-02-22 19:28 ` Eli Zaretskii
2021-02-22 20:28 ` Joost Kremers
2021-02-22 21:49 ` Dmitry Gutov [this message]
2021-02-22 21:57 ` Lars Ingebrigtsen
2021-02-22 22:30 ` [External] : " Drew Adams
2021-02-23 0:45 ` Stefan Kangas
2021-02-23 5:34 ` Drew Adams
2021-02-23 5:46 ` Drew Adams
2021-02-23 5:54 ` Peter Dean
2021-02-23 15:22 ` Eli Zaretskii
2021-02-23 15:29 ` Peter Dean
2021-02-23 16:00 ` Eli Zaretskii
2021-02-23 17:32 ` Peter Dean
2021-02-23 17:40 ` Eli Zaretskii
2021-02-23 17:59 ` Peter Dean
2021-02-23 18:26 ` Eli Zaretskii
2021-02-23 19:36 ` Peter Dean
2021-02-23 19:46 ` Eli Zaretskii
2021-02-23 21:58 ` Peter Dean
2021-02-24 3:25 ` Eli Zaretskii
2021-02-27 21:44 ` Dmitry Gutov
2021-02-28 17:32 ` Eli Zaretskii
2021-03-01 5:22 ` Richard Stallman
2021-02-23 5:44 ` Drew Adams
2021-02-23 14:18 ` Lars Ingebrigtsen
2021-02-23 15:44 ` Drew Adams
2021-02-23 16:15 ` Stefan Kangas
2021-02-23 16:28 ` Drew Adams
2021-02-22 21:19 ` Stefan Kangas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84e3f5ab-436e-c0ea-39f1-2466f3227910@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=laszlomail@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.