From: Drew Adams <drew.adams@oracle.com>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, Yuri Khan <yuri.v.khan@gmail.com>
Subject: RE: display value of links in mini-buffer (was: Re: bug archiving policy)
Date: Sun, 6 Dec 2020 11:58:12 -0800 (PST) [thread overview]
Message-ID: <6f616cf3-8439-4493-9a15-5bcef8dd0841@default> (raw)
In-Reply-To: <20201206182756.pd2upjcd5dl4gbal@E15-2016.optimum.net>
> This speaks to a prior long thread about the user-friendliness of emacs
> to new users, in that the keybinding hints are useful to new users and
> a nice reminder to experienced users who have stepped away from use long
> enough to forget, but once the keybindings are learned the keybinding
> hints lose ALL value for that user and Yuri's type of suggestion for
> supplemental information becomes more useful.
Your general point may make some sense. Certainly
repeated use of something makes reminders about it
less useful.
But it's true not only just case by case for a
given user, but case by case for specific contexts.
For example, a `mouse-1' action reminder in Dired
is different from the same elsewhere, whether or
not the action itself is similar. And even for a
given user, things change over time, including use
patterns/habits and awareness. They can change not
only in the direction of less need of a reminder.
The answer to this kind of thing at a general level
is to provide more user control. There are various
ways of doing that, from providing feedback levels
(degrees) to providing customization of specific
kinds of feedback.
One size may not fit all, but for now we have one
size, and it should fit most, and in particular most
who are not too familiar with the given context.
next prev parent reply other threads:[~2020-12-06 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<CAP_d_8XG7BrPqC3ZsqijLZerTOgPwt_MeBZOkDCbCuk6_cgGKQ@mail.gmail.com>
[not found] ` <<83zh2r9n26.fsf@gnu.org>
[not found] ` <<CAP_d_8WezomrMT6U+H5_R8P9d3=_Vm98S_4y0Hw-oTaL5n+hsA@mail.gmail.com>
[not found] ` <<83wnxv9lcy.fsf@gnu.org>
2020-12-06 16:42 ` display value of links in mini-buffer (was: Re: bug archiving policy) Drew Adams
2020-12-06 18:27 ` Boruch Baum
2020-12-06 19:58 ` Drew Adams [this message]
2020-12-06 10:54 Yuri Khan
2020-12-06 11:07 ` Boruch Baum
2020-12-06 11:26 ` Eli Zaretskii
2020-12-06 11:35 ` Boruch Baum
2020-12-06 11:39 ` Eli Zaretskii
2020-12-06 11:51 ` Yuri Khan
2020-12-06 12:03 ` Eli Zaretskii
2020-12-06 11:44 ` Eli Zaretskii
2020-12-06 12:04 ` Yuri Khan
2020-12-06 12:20 ` Eli Zaretskii
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=6f616cf3-8439-4493-9a15-5bcef8dd0841@default \
--to=drew.adams@oracle.com \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@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).