unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: MINI-PATCH: add how to turn auto-completion in test buffers off
Date: Mon, 8 Apr 2024 07:30:10 +0200	[thread overview]
Message-ID: <CAO48Bk8Lo=1a=gVL9GrnfptbgWyWpZdDrEMs5bWNBPfixLRLnw@mail.gmail.com> (raw)
In-Reply-To: <86zfu5z93q.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]

On Sun, 7 Apr 2024 at 13:49, Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> > Date: Sun, 7 Apr 2024 12:57:31 +0200
> > Cc: emacs-devel@gnu.org
> >
> >  > Is there any conceptual difference between providing
> flyspell/ispell-mode and providing
> >  > auto-complete suggestions in text mode?
> >
> >  Yes, there is: auto-complete suggestions happen _before_ you type,
> >  whereas Flyspell happens _after_ you type.
> >
> > But is that enough to make the activation/deactivation process so
> different?
> > I mean. currently, if you want flyspell-mode for a specific mode, you
> > add
> > ```
> > (flyspell-mode 1)
> > ```
> > to the hook function with the rest of the customisations for that mode.
> > Now, for auto-complete it goes the other way round... you need to add
> code
> > to disable it and that is confusing (al4m).
>
> Sorry, I don't see the big difference.  Flyspell-mode is off by
> default, whereas completion hints are on by default, that's all.
>

I feel different... The way of turning auto-complete based on ispell off is
less obvious
reading/writing the code that turns flyspell on.


> > I missed it... (bad memories from the time when it took place) but yes,
> I'd like to be convinced why this feature
> > needs to be activated by default.
>
> Because we considered it to be very useful.
>

Yes, but there are situations where this feature may discourage people from
using Emacs... because it
distracts from the task you are performing, because it produces much more
additional output that needs
to be treated by the interface, etc. Once again, all these are
distractions. In the best case they are a nuisance,
but depending on specific conditions they may lead to a person failing to
produce a document or even
worse.

Best, /PA

PS: Anecdote: I've given it a try it for my work in several languages, and
the hit rate was really low. Most of the
time it was just for fun that I looked at the suggestions and I had some
candidates that are off-limits in any
well-mannered conversation ;-)

-- 
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 3453 bytes --]

  reply	other threads:[~2024-04-08  5:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 17:29 MINI-PATCH: add how to turn auto-completion in test buffers off Pedro Andres Aranda Gutierrez
2024-04-04 18:48 ` Eli Zaretskii
2024-04-05 10:25   ` Pedro Andres Aranda Gutierrez
2024-04-05 12:41     ` Eli Zaretskii
2024-04-05 15:02       ` Pedro Andres Aranda Gutierrez
2024-04-07  6:32         ` Pedro Andres Aranda Gutierrez
2024-04-07  8:00           ` Eli Zaretskii
2024-04-07 10:57             ` Pedro Andres Aranda Gutierrez
2024-04-07 11:48               ` Eli Zaretskii
2024-04-08  5:30                 ` Pedro Andres Aranda Gutierrez [this message]
2024-04-08 11:27                   ` Eli Zaretskii
2024-04-08 16:56                     ` Pedro Andres Aranda Gutierrez
2024-04-08 17:37                       ` tomas
2024-04-08 18:38                         ` Eli Zaretskii
2024-04-08 18:43                           ` Emanuel Berg
2024-04-09  4:31                             ` tomas
2024-04-09  5:06                               ` Emanuel Berg
2024-04-09  9:26                                 ` Eli Zaretskii
2024-04-09  9:32                                   ` tomas
2024-04-08 17:57                       ` Eli Zaretskii
2024-04-09  5:22                         ` Pedro Andres Aranda Gutierrez
2024-04-10  8:45                           ` Pedro Andres Aranda Gutierrez
2024-04-10 13:07                             ` Eli Zaretskii
2024-04-10 13:35                               ` tomas
2024-04-10 13:58                                 ` Eli Zaretskii
2024-04-10 14:10                                   ` tomas
2024-04-10 14:45                                     ` Pedro Andres Aranda Gutierrez
2024-04-10 15:26                                     ` 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='CAO48Bk8Lo=1a=gVL9GrnfptbgWyWpZdDrEMs5bWNBPfixLRLnw@mail.gmail.com' \
    --to=paaguti@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).