unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: Po Lu <luangruo@yahoo.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Eli Zaretskii <eliz@gnu.org>,
	emacs-devel@gnu.org
Subject: Re: Question about completion behavior
Date: Thu, 10 Mar 2022 11:21:57 +0100	[thread overview]
Message-ID: <20220310102157.wmmn7bkkdbux7aug@Ergus> (raw)
In-Reply-To: <87lexiiqnk.fsf@yahoo.com>

Hi Po:

On Thu, Mar 10, 2022 at 08:42:55AM +0800, Po Lu wrote:
>Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
>> Then again, it's only by enabling it by default that we'll get a clear
>> picture of which changes are annoyances are which aren't.
>>
>> So I'd start by changing the default on `master` and after a month or
>> so, collect feedback to decide how to go about adding it: either by just
>> changing the behavior willy-nilly, or introduce it but add an option to
>> revert to the old behavior, or leave the default unchanged but add an
>> option to get the new behavior, ...
>
>This really doesn't warrant month-long experiments.  Larger changes like
>variable-pitch modelines might, but IMHO this is too small a change.
>
If it is small, then should be easier to do. Maybe?

Bigger changes on defaults are actually almost impossible to agree for
what I have seen these years. That's why I only try small ones now.

This changes make the new user's experience consistent and just a bit
more dynamic. Ex: going for the 'visible alternative is such a subtle
change that 50% of the users may not even note it.

Old users usually know how to add 1 line to their config if they really
feel annoyed and want to revert. But most of them use
ido/vertico/selectrum/ivy or something else (for a reason btw).

>I would prefer just adding an option to get the new behavior, and asking
>people to try that.
>
(Please ignore the next part if you want as it is totally off-topic)

One of the main issues in Emacs (we have discussed in this same mailing
list several times) is that communication with the community and
external developers is not very efficient. I won't expect emacs to be a
rockstart, but at least a country artist with some seasonal fashion from
time to time.

On every release the NEWS file is so long and most changes are cryptic
for external users; the manual is usually more difficult to explore
(almost impossible to find, or search in for a new user) and the first
impression is in general very bad. I have new students every year and I
try them to use emacs, after a while I notice that they only "stand it"
because (and while) I insist, some of them try external inits from
github to start, some others try customizations like spacemacs or
similes... but at the end all of them end using vim, vscode and so on.

Many of the defaults are very "archaic"... and some are like that
because of hardware limitations from 20-30 years ago. As it is not on
github, contributing, feature requests and issues report system is very
unfamiliar for any <30 years old user and the releases take so long and
contain so many changes (most of them hidden by default) that we still
have users that use the external packages like linum or
fill-column-indicator...

In conclusion we don't have any effective way to "to ask the people to
try" things that maybe they need.

>Thanks.
>
Best,
Ergus



  reply	other threads:[~2022-03-10 10:21 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220309001013.gxyh2uasbuxiz6ww.ref@Ergus>
2022-03-09  0:10 ` Question about completion behavior Ergus
2022-03-09  0:22   ` Stefan Monnier
2022-03-09  1:46     ` Ergus
2022-03-09  3:05       ` Stefan Monnier
2022-03-09  3:37         ` Eli Zaretskii
2022-03-09 10:11           ` Ergus
2022-03-09 11:46             ` Ergus
2022-03-09 13:16               ` Eli Zaretskii
2022-03-09 13:46                 ` Po Lu
2022-03-09 17:32                   ` Stefan Monnier
2022-03-09 17:41                     ` Ergus
2022-03-10  0:42                     ` Po Lu
2022-03-10 10:21                       ` Ergus [this message]
2022-03-10 11:15                         ` Po Lu
2022-03-10 14:03                           ` Ergus
2022-03-10 18:50                             ` Juri Linkov
2022-03-10 22:35                               ` Ergus
2022-03-12 18:31                                 ` Juri Linkov
2022-03-13 14:58                                   ` Ergus
2022-03-12  0:17                               ` Ergus
2022-03-12 18:34                                 ` Juri Linkov
2022-03-13 11:21                                   ` Ergus
2022-03-13 17:44                                     ` Juri Linkov
2022-03-13 18:50                                       ` Ergus
2022-03-13 18:57                                         ` Eli Zaretskii
2022-03-13 19:49                                           ` Ergus
2022-03-13 20:48                                       ` [External] : " Drew Adams
2022-03-13 21:15                                         ` Ergus
2022-03-13 23:14                                           ` Drew Adams
2022-03-13 23:38                                             ` Ergus
2022-03-14  2:23                                               ` Drew Adams
2022-03-12 20:25                             ` Drew Adams
2022-03-09 14:30                 ` Ergus
2022-03-09 16:14                   ` [PATCH] " Ergus
2022-03-09 16:56                   ` Eli Zaretskii
2022-03-09 13:10             ` Eli Zaretskii
2022-03-09 14:22               ` Ergus

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=20220310102157.wmmn7bkkdbux7aug@Ergus \
    --to=spacibba@aol.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.com \
    --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).