unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Mendler <daniel@mendler.net>
Cc: JD Smith <jdtsmith@gmail.com>,  emacs-devel@gnu.org
Subject: Re: Recommendation for CAPF setup when you don't know completion string in advance
Date: Tue, 11 May 2021 11:57:43 -0400	[thread overview]
Message-ID: <jwvv97pnu6c.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <488b4688-239f-4915-a1fa-a1c3764234d1@mendler.net> (Daniel Mendler's message of "Tue, 11 May 2021 16:37:42 +0200")

> ;; XXX There is a small bug here, depending on interpretation. When
> ;; completing "~/emacs/master/li|/calc" where "|" is the cursor,
> ;; then the returned candidate only includes the prefix
> ;; "~/emacs/master/lisp/", but not the suffix "/calc". Default
> ;; completion has the same problem when selecting in the
> ;; *Completions* buffer.
>
> Is it non-intentional that the suffix is thrown away?

I think the answer depends on the completion-style.  IIRC some
completion styles do that on purpose (in order to preserve/reproduce
the behavior of earlier completion code), whereas I seem to remember
a few cases where we may do something like that not on purpose (rather
because of a bug, or out of laziness).


        Stefan




  reply	other threads:[~2021-05-11 15:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03 22:23 Recommendation for CAPF setup when you don't know completion string in advance JD Smith
2021-04-03 23:49 ` Stefan Monnier
2021-04-04  2:52   ` JD Smith
2021-04-04  3:20     ` Stefan Monnier
2021-04-04 15:29       ` JD Smith
2021-05-11  3:33   ` JD Smith
2021-05-11  4:04     ` Stefan Monnier
2021-05-11 13:42       ` JD Smith
2021-05-11 15:52         ` Stefan Monnier
2021-05-11 14:37       ` Daniel Mendler
2021-05-11 15:57         ` Stefan Monnier [this message]
2021-05-11 16:10           ` Daniel Mendler
2021-05-11 16:54             ` Stefan Monnier

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=jwvv97pnu6c.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=daniel@mendler.net \
    --cc=emacs-devel@gnu.org \
    --cc=jdtsmith@gmail.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).