unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Politz <politza@hochschule-trier.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29007@debbugs.gnu.org
Subject: bug#29007: 25.3; [PATCH] Make filecache use extended completion
Date: Sat, 04 Nov 2017 18:44:43 +0100	[thread overview]
Message-ID: <874lqa3pmc.fsf@hochschule-trier.de> (raw)
In-Reply-To: <83fu9vuq54.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 03 Nov 2017 21:19:03 +0200")


OK, I'll elaborate.

Currently, file-cache-minibuffer-complete does longest-prefix completion
via all-completions only, instead of completion-all-completions, which
completes according to the completion-styles variable.  And here are
some cases where this behavior is inconvenient or even insufficient,
when trying to open some file via `C-x C-f C-TAB'.

1. Opening some file from the file-cache, without remembering the exact
   prefix.

   Example: You only remember that the file ends in '-foo.el'.

2. Opening some file, while the file-cache contains many files having the
   same prefix.

   Example: The cache contains the following files.
   
   aaa.a
   aab.b
   aba.c
   abb.d
   baa.e
   bab.f
   bba.g
   bbb.h

   Here prefix completion is basically useless, but entering the unique
   suffix and using substring completion immediately completes to the
   unique match.

-ap





  reply	other threads:[~2017-11-04 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26  6:56 bug#29007: 25.3; [PATCH] Make filecache use extended completion Andreas Politz
2017-11-03  9:56 ` Eli Zaretskii
2017-11-03 17:12   ` Andreas Politz
2017-11-03 19:19     ` Eli Zaretskii
2017-11-04 17:44       ` Andreas Politz [this message]
2017-11-04 18:23         ` Eli Zaretskii
2017-11-04 19:31           ` Andreas Politz
2017-11-04 19:48             ` Eli Zaretskii
2017-11-04 20:53               ` Andreas Politz

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=874lqa3pmc.fsf@hochschule-trier.de \
    --to=politza@hochschule-trier.de \
    --cc=29007@debbugs.gnu.org \
    --cc=eliz@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).