From: martin rudalics <rudalics@gmx.at>
To: "N. Jackson" <nljlistbox2@gmail.com>
Cc: 23092@debbugs.gnu.org
Subject: bug#23092: 25.0.92; Minibuffer completion fails to resize completion window if reused during same command
Date: Wed, 23 Mar 2016 19:53:59 +0100 [thread overview]
Message-ID: <56F2E647.7040400@gmx.at> (raw)
In-Reply-To: <878u19gn38.fsf@gmail.com>
>> Obviously, the second branch is based on the assumption that a user will
>> "refine" her completions in the sense that she starts with a large
>> number of possible completions and, by typing characters in the
>> minibuffer, reduces the number of possible completions until she found
>> the right one.
>
> This is a valid assumption and basis of design when the completion is of
> something like a command or a function name, because then the completion
> list is gradually narrowed.
>
> But in the case of completion of a file path, this assumption is not
> valid. (And completing each directory name down a file path is a
> perfectly normal use case.) The difference is that one is not doing a
> single completion but several discrete completions.
I'm not sure whether we should by default change something in this case.
Juri has designed the present concept and I would rather leave it to him
how to proceed.
> For example, I was doing a find-file to find something in my Emacs init.
> I started with `~/.em TAB' expecting a single match of ~/.emacs.d/ but
> instead (of course) I got the initial completions window with .emacs and
> .emacs.d in it -- a very small completions window. Then I needed a
> subdirectory in ~/.emacs.d/ but couldn't remember its name at all, so I
> hit TAB again and got the entire contents of emacs.d/ which is a very
> long list [it seems to be jammed up full of session files for some
> reason] all displayed in a buffer sized to show one line of
> completion candidates.
Does enabling ‘temp-buffer-resize-mode’ handle that case sufficiently
well?
>> Apparently, the OP works in the opposite direction - he starts with
>> few suggestions and removes characters from the minibuffer ending up
>> with more and more suggestions.
>
> No, not normally. When I was trying to come up with a simple
> reproducible recipe I wanted an example in the emacs tree, and the
> example I was able to up with was a bit contrived. (Although I don't
> think it's an unlikely use case.)
Let's wait for Juri to chime in. Meanwhile please have a look at the
manual changes I proposed. (I don't even know if the example works as
intended.)
martin
next prev parent reply other threads:[~2016-03-23 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 17:07 bug#23092: 25.0.92; Minibuffer completion fails to resize completion window if reused during same command N. Jackson
2016-03-22 17:21 ` martin rudalics
2016-03-22 18:42 ` N. Jackson
2016-03-22 18:53 ` martin rudalics
2016-03-22 19:56 ` N. Jackson
2016-03-22 20:10 ` Eli Zaretskii
2016-03-22 21:06 ` N. Jackson
2016-03-22 18:28 ` Eli Zaretskii
2016-03-22 18:55 ` N. Jackson
2016-03-22 19:04 ` Eli Zaretskii
2016-03-22 20:07 ` N. Jackson
2016-03-23 8:09 ` martin rudalics
2016-03-23 16:45 ` N. Jackson
2016-03-23 18:53 ` martin rudalics [this message]
2016-03-23 20:34 ` N. Jackson
2016-03-23 21:27 ` Juri Linkov
2016-03-24 7:43 ` martin rudalics
2016-03-24 22:14 ` Juri Linkov
2016-03-25 7:42 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56F2E647.7040400@gmx.at \
--to=rudalics@gmx.at \
--cc=23092@debbugs.gnu.org \
--cc=nljlistbox2@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.