From: nljlistbox2@gmail.com (N. Jackson)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23092@debbugs.gnu.org
Subject: bug#23092: 25.0.92; Minibuffer completion fails to resize completion window if reused during same command
Date: Tue, 22 Mar 2016 18:06:19 -0300 [thread overview]
Message-ID: <87lh5agr3o.fsf@gmail.com> (raw)
In-Reply-To: <83y49a2s0i.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Mar 2016 22:10:21 +0200")
At 22:10 +0200 on Tuesday 2016-03-22, Eli Zaretskii wrote:
>> From: nljlistbox2@gmail.com (N. Jackson)
>> Date: Tue, 22 Mar 2016 16:56:03 -0300
>> Cc: 23092@debbugs.gnu.org
>>
>> > displaying two, three completions in a window that occupies one half
>> > of your frame does not strike me as a good solution either.
>>
>> For me though, this seems absolutely fine. After all that window is only
>> there until I've finished my command in the minibuffer, then it
>> disappears.
>
> In theory, yes. In practice, it's all too easy to cause it be left in
> place long after you have no use for that buffer. I'm sure it
> happened to you at least once.
Actually, no, I haven't had that problem yet, not caused by the
completions window at least; it seems to consistently close when I
finish the command in the minibuffer.
>> (If it was taking up so much space that it prevented me from seeing
>> something I needed to refer to while completing my command in the
>> minibuffer, that would be another matter entirely, but with the
>> completions window occupying the right half of the frame that was never
>> an issue for me in Emacs 24.)
>
> Having it occupy half the frame, obscuring too much of the buffer I'm
> editing, is also an annoyance.
Yes, obscuring the buffer being edited is an annoyance. I suppose the
circumstances when it occurs depends on the user's set up.
In my usage I almost always use a small laptop and the display is
sufficiently small that it's easiest to keep all my Emacs frames
maximised. The display has a 16:9 rather than a 4:3 (16:12) ratio, so
I'm rather limited in height compared to width. A full height window
here is only 48 characters high.
When my frame gets split-right, I get two windows that are both about 92
characters wide, so a completions window on the right rarely obscures
_any_ of the window I'm editing (which is typically displaying lines of
text 72- or 80-characters long).
On the other hand, the new behaviour of splitting the completion window
below is guaranteed to obscure part of the window I'm editing.
next prev parent reply other threads:[~2016-03-22 21:06 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 [this message]
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
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
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=87lh5agr3o.fsf@gmail.com \
--to=nljlistbox2@gmail.com \
--cc=23092@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).