unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 62836@debbugs.gnu.org
Subject: bug#62836: [PATCH] Provide an example of using fuzzier completion.
Date: Sat, 15 Apr 2023 11:34:57 +0300	[thread overview]
Message-ID: <83a5z9ee6m.fsf@gnu.org> (raw)
In-Reply-To: <ierzg7acxst.fsf@janestreet.com> (message from Spencer Baugh on Fri, 14 Apr 2023 11:01:54 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Fri, 14 Apr 2023 11:01:54 -0400
> 
> >From b8d081b19cb46965c6fc170253702c53d53f2ee2 Mon Sep 17 00:00:00 2001
> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Fri, 14 Apr 2023 10:58:17 -0400
> Subject: [PATCH] Provide an example of using fuzzier completion.
> 
> In my experience, new users of vanilla Emacs often complain about the
> lack of fuzzy completion by default.  However, the "basic" completion
> style provides a decent amount of fuzziness out of the box.  We should
> explain this a little more to users.  (I myself have often had to
> explain this.)

Are the examples you suggest to add really considered as "fuzzy
completion"?

> +  @key{TAB} also works while point is not at the end of the
> +minibuffer.  If you type @kbd{M-x a u t o c m o d e}, then @kbd{C-b}
> +several times to move point back before the @samp{mode}, you can hit
> +@key{TAB} to insert text between @samp{autoc} and @samp{mode}
> +so that the minibuffer contains @code{autoconf-mode}.
> +
> +  When point is not at the end of the minibuffer and you hit
> +@kbd{TAB}, completion will fill in text both at point and at the end
> +of the minibuffer.  So you could also type @kbd{M-x a u t o c m o},
> +@kbd{C-b} twice to move point back before the @samp{mo}, and then
> +@key{TAB} will insert the text @samp{onf-} at point and @samp{de} at
> +the end of the minibuffer, so that the minibuffer contains
> +@code{autoconf-mode}.

I'd prefer to have only the second example, as it demonstrates the
more general behavior, which includes the one described by the first
example.

Also, we use @kbd{M-x autocmo}, without the spaces between characters,
in such cases.  (It is actually enough to type "M-x autocm" followed
by a single C-b, to show the behavior in this case.)

Please be consistent about your markup: if you use @samp{onf-},
pleased also use @samp{autoconf-mode}.

Finally, please use @kbd{@key{TAB}} in the context that calls for the
user to press the TAB key.

Thanks.





  reply	other threads:[~2023-04-15  8:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 15:01 bug#62836: [PATCH] Provide an example of using fuzzier completion Spencer Baugh
2023-04-15  8:34 ` Eli Zaretskii [this message]
2023-04-15 22:22   ` sbaugh
2023-04-16  5:57     ` Eli Zaretskii
2023-04-18 22:07       ` Spencer Baugh
2023-04-19 12: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=83a5z9ee6m.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62836@debbugs.gnu.org \
    --cc=sbaugh@janestreet.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).