all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org, Stephen Berman <stephen.berman@gmx.net>
Subject: Re: Upcoming merge of adaptive-wrap
Date: Sat, 27 Jan 2024 18:56:46 +0200	[thread overview]
Message-ID: <063e35f8-5920-4899-8b48-2a86c524b70e@gutov.dev> (raw)
In-Reply-To: <87a5orl95m.fsf@yahoo.com>

On 27/01/2024 05:58, Po Lu wrote:
> Dmitry Gutov <dmitry@gutov.dev> writes:
> 
>> But would they, largely? You actually have to visit the directory
>> which hosts NEWS on your system (where is it installed to?), mark all
>> previous NEWS files and do the search. That's non-trivial.
> 
> Is this meant to imply that selecting "Help -> Emacs News", then typing
> `C-x d' is non-trivial?  What about reading the manual, or any other of
> Emacs's built-in facilities for assisting users?

It's an order of a magnitude more involved than 'M-x list-packages' 
followed by C-s.

> When users are stumped, their first reactions are to reach for the
> documentation, be that the manual, apropos or NEWS.

Through Google -- maybe.

> It also stands to reason that users outside the first two categories are
> more inclined to take to a search engine, and to them this thread will
> be more enlightening than the package menu ever will.

Because its title is a good match for whatever the user would search 
for? What would they search for, BTW?

>> If you sit every user behind a screen and force them to read either of
>> the texts entirely, sure. But that's not how it usually works.
> 
> [...]
> 
>> It's a good explanation (easier to understand than the summary, I
>> agree), but I'm curious what would you improve in the summary to make
>> it more recognizable. Any particular keywords? From where I'm
>> standing, even after reading the description, all the important ones
>> seem to be there: "wrap", "adaptive", "line-wrapping", "wrap-prefix".
> 
> I never proposed to improve the summary, since in my opinion, the
> current package description is already the optimum under the limitations
> of its format.

You renamed the package to visual-wrap, so perhaps the term "visual" 
could help (instead of "smart"?).

There's also a mistake in the description now: visual-fill-mode does not 
exist.

>> Even if you're reading the NEWS, you probably don't carefully scan
>> every entry, so there must be some particular words which might have
>> piqued your interest in the way that the current summary does not.
> 
> The mental effort required to understand the NEWS and the documentation
> I installed is so little that, truly, the only words left to be said are
> "there are none so blind as those who will not see", assuming that the
> reader is searching for this feature.

The issue is not reading a particular NEWS entry, but finding it.



  reply	other threads:[~2024-01-27 16:56 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=063e35f8-5920-4899-8b48-2a86c524b70e@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --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 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.