unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, 38476@debbugs.gnu.org
Subject: bug#38476: 27.0.50; substring completion feature request
Date: Fri, 20 May 2022 14:34:16 +0200	[thread overview]
Message-ID: <878rqw2xiv.fsf@gnus.org> (raw)
In-Reply-To: <87h75k1j88.fsf@gmx.net> (Stephen Berman's message of "Fri, 20 May 2022 14:28:23 +0200")

Stephen Berman <stephen.berman@gmx.net> writes:

> 0. $ mkdir /tmp/test; touch /tmp/test/{file1test,file2test}
> 1. $ emacs-master -Q --eval "(setq completion-category-overrides
>      '((buffer (styles substring)) (file (styles substring))))"
> 2. Type `C-x C-f /tmp/test/te TAB'
> => The minibuffer displays the following, with point at the end of the line:
>
> Find file: /tmp/test/test

Thanks.  With that recipe, I can reproduce the behaviour.

> Typing TAB a second time pops up a the *Completions* buffer showing
> file1test and file2test as the two possible completions.  But to
> complete either of these in the minibuffer you have to move point.
> That's the bug (or feature request).

Yeah, that doesn't seem like the best place to put point.

>> With "*te TAB" it completes to file*test with point after *, which seems
>> correct, too.
>
> Yes, that input didn't occur to me when I filed the report.  I just now
> scrolled through the Completion node of the Emacs manual and didn't see
> a reference to it; is it documented?  If not, perhaps it should be.

I think I've learned about * through osmosis -- perhaps it isn't
documented?  But it definitely should be.

> Anyway, using * comes close to satisfying the feature request, so if
> it's too hard to make it work without the *, I can live with having to
> use *.

It'd be nice if `substring' placed point where the * thing does, but
perhaps there are reasons for the current behaviour...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-05-20 12:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03 19:32 bug#38476: 27.0.50; substring completion feature request Stephen Berman
2022-05-20 11:39 ` Lars Ingebrigtsen
2022-05-20 12:28   ` Stephen Berman
2022-05-20 12:34     ` Lars Ingebrigtsen [this message]

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=878rqw2xiv.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=38476@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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 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).