From: Po Lu <luangruo@yahoo.com>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: emacs-devel@gnu.org, Stephen Berman <stephen.berman@gmx.net>
Subject: Re: Upcoming merge of adaptive-wrap
Date: Sun, 28 Jan 2024 17:34:38 +0800 [thread overview]
Message-ID: <87y1c9hkcx.fsf@yahoo.com> (raw)
In-Reply-To: <063e35f8-5920-4899-8b48-2a86c524b70e@gutov.dev> (Dmitry Gutov's message of "Sat, 27 Jan 2024 18:56:46 +0200")
Dmitry Gutov <dmitry@gutov.dev> writes:
> It's an order of a magnitude more involved than 'M-x list-packages'
> followed by C-s.
And installing Emacs was no doubt several orders of magnitude more so.
> Through Google -- maybe.
This assessment of our users' problem-solving capabilities is not the
correct attitude to take in developing Emacs, or any software that is
not expressly designed for such individuals, as from it the logical
conclusion to draw is that there is no value in documentation itself.
How would they learn of the existence of the package list, for instance,
or where to click and what to type to display it?
> Because its title is a good match for whatever the user would search
> for? What would they search for, BTW?
The emails in this thread contain every word present in the package list
summary, so presumably the same words they would search for within the
package list; but that was meant as a rhetorical statement, not to be
taken literally.
> You renamed the package to visual-wrap, so perhaps the term "visual"
> could help (instead of "smart"?).
Not really. The room available in package descriptions is inadequate:
descriptions are more helpful than a list of keywords, which is the best
that can be hoped in that limited space.
> There's also a mistake in the description now: visual-fill-mode does
> not exist.
Thanks.
> The issue is not reading a particular NEWS entry, but finding it.
There are none so blind as those who will not venture to see.
But fortunately for us, incorrigibly blind (in this sense) individuals
are far and few between.
next prev parent reply other threads:[~2024-01-28 9:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <878r4eqjh8.fsf.ref@yahoo.com>
2024-01-25 1:39 ` Upcoming merge of adaptive-wrap Po Lu
2024-01-25 4:44 ` Adam Porter
2024-01-25 10:01 ` Stephen Berman
2024-01-25 11:32 ` Po Lu
2024-01-25 12:37 ` Eli Zaretskii
2024-01-25 13:15 ` Po Lu
2024-01-26 8:05 ` Kévin Le Gouguec
2024-01-26 10:21 ` Po Lu
2024-01-26 11:26 ` Joost Kremers
2024-01-26 12:40 ` Eli Zaretskii
2024-01-26 13:47 ` Joost Kremers
2024-01-31 19:18 ` Stefan Monnier
2024-02-02 4:41 ` Madhu
2024-02-02 7:22 ` Eli Zaretskii
2024-01-25 17:10 ` Dmitry Gutov
2024-01-25 20:01 ` Stefan Kangas
2024-01-25 20:11 ` Dmitry Gutov
2024-01-26 1:45 ` Po Lu
2024-01-26 2:08 ` Dmitry Gutov
2024-01-26 2:22 ` Po Lu
2024-01-26 2:30 ` Dmitry Gutov
2024-01-26 4:03 ` Po Lu
2024-01-27 1:44 ` Dmitry Gutov
2024-01-27 3:58 ` Po Lu
2024-01-27 16:56 ` Dmitry Gutov
2024-01-27 22:59 ` Stefan Kangas
2024-01-28 0:18 ` [External] : " Drew Adams
2024-01-28 9:02 ` Michael Albinus
2024-01-28 9:36 ` Po Lu
2024-01-28 13:03 ` Dmitry Gutov
2024-01-29 1:56 ` Po Lu
2024-01-28 15:32 ` Drew Adams
2024-01-28 9:34 ` Po Lu [this message]
2024-01-28 13:11 ` Dmitry Gutov
2024-01-28 14:25 ` Po Lu
2024-01-28 18:01 ` Dmitry Gutov
2024-01-29 1:55 ` Po Lu
2024-01-26 1:54 ` Po Lu
2024-01-26 7:50 ` Eli Zaretskii
2024-01-26 10:24 ` Po Lu
2024-01-25 20:05 ` 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
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=87y1c9hkcx.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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).