From: nljlistbox2@gmail.com (N. Jackson)
To: martin rudalics <rudalics@gmx.at>
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 17:34:50 -0300 [thread overview]
Message-ID: <87egb1exw5.fsf@gmail.com> (raw)
In-Reply-To: <56F2E647.7040400@gmx.at> (martin rudalics's message of "Wed, 23 Mar 2016 19:53:59 +0100")
At 19:53 +0100 on Wednesday 2016-03-23, martin rudalics wrote:
>
> 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.
By all means. I just felt it was my "duty" to point out what might (or
might not) be an oversight in the design.
> Does enabling ‘temp-buffer-resize-mode’ handle that case sufficiently
> well?
Yes after a day of use, I can say that `temp-buffer-resize-mode'
provides much better behaviour (IMO), and properly supports the type of
use cases I mentioned.
However the point is moot (for this user at least), because with your
code from bug#23093, viz.
(customize-set-variable
'display-buffer-alist
'(("\\*Completions\\*" display-buffer-pop-up-window)))
I get my completions buffer on the right half of my frame, and it would
not make sense for that to change size (I wouldn't like it, anyway), so
I won't need to use `temp-buffer-resize-mode'.
Thanks.
Regards,
N.
next prev parent reply other threads:[~2016-03-23 20:34 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
2016-03-23 20:34 ` N. Jackson [this message]
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=87egb1exw5.fsf@gmail.com \
--to=nljlistbox2@gmail.com \
--cc=23092@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).