From: martin rudalics <rudalics@gmx.at>
To: Juri Linkov <juri@jurta.org>
Cc: 17809@debbugs.gnu.org
Subject: bug#17809: 24.4.50; Completions display
Date: Wed, 25 Jun 2014 08:54:26 +0200 [thread overview]
Message-ID: <53AA7222.1010905@gmx.at> (raw)
In-Reply-To: <87y4wlg8gx.fsf_-_@mail.jurta.org>
> I tried to do this in bug#17809, but stumbled on the problem
> that resizing the window after filling is not supported
> by display-buffer actions alist.
`display-buffer' obviously expects the buffer to be "ready" at the time
of fitting the window to it.
>> For `with-temp-buffer-window' this means that we would have to fill the
>> buffer either via `temp-buffer-window-show-hook' or in QUIT-FUNCTION.
>
> Maybe filling the buffer is possible in QUIT-FUNCTION, but instead of
> `with-temp-buffer-window', `minibuffer-completion-help' uses
> `with-output-to-temp-buffer' that has no QUIT-FUNCTION arg.
Then `temp-buffer-show-hook' should cut it.
martin
next prev parent reply other threads:[~2014-06-25 6:54 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 13:30 bug#17831: 24.4.50; bad default value for `Man-width' Leo Liu
2014-06-23 12:53 ` Stefan Monnier
2014-06-23 23:17 ` Juri Linkov
2014-06-24 1:26 ` Stefan Monnier
2014-06-24 7:13 ` martin rudalics
2014-06-24 12:53 ` Stefan Monnier
2014-06-24 15:55 ` Eli Zaretskii
2014-06-24 17:33 ` Stefan Monnier
2014-06-24 17:59 ` Eli Zaretskii
2014-06-25 6:54 ` martin rudalics
2014-06-24 15:46 ` Eli Zaretskii
2014-06-24 17:31 ` Stefan Monnier
2014-06-24 17:56 ` Eli Zaretskii
2014-06-24 19:35 ` Stefan Monnier
2014-06-24 20:06 ` Eli Zaretskii
2014-06-24 20:29 ` Stefan Monnier
2014-06-24 23:48 ` Juri Linkov
2014-06-25 3:11 ` Stefan Monnier
2014-06-26 23:49 ` Juri Linkov
2014-06-27 2:16 ` Stefan Monnier
2014-06-27 23:45 ` Juri Linkov
2014-06-28 1:30 ` Stefan Monnier
2014-06-29 23:42 ` Juri Linkov
2014-06-30 3:29 ` Stefan Monnier
2014-06-24 23:42 ` Juri Linkov
2014-06-25 6:54 ` martin rudalics
2014-06-24 23:44 ` bug#17809: 24.4.50; Completions display Juri Linkov
2014-06-25 6:54 ` martin rudalics [this message]
2014-06-26 23:41 ` Juri Linkov
2014-06-27 2:07 ` Stefan Monnier
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:54 ` Juri Linkov
2014-06-28 8:18 ` martin rudalics
2014-06-29 23:47 ` Juri Linkov
2014-07-01 23:30 ` Juri Linkov
2014-07-04 23:40 ` Juri Linkov
2014-07-06 4:32 ` Stefan Monnier
2014-07-06 23:32 ` Juri Linkov
2014-07-07 1:21 ` Stefan Monnier
2014-07-07 1:24 ` Stefan Monnier
2014-07-07 6:49 ` Juri Linkov
2014-07-08 3:43 ` Stefan Monnier
2014-07-08 8:03 ` Juri Linkov
2014-06-27 6:43 ` martin rudalics
2014-06-27 23:53 ` Juri Linkov
2014-06-28 8:17 ` martin rudalics
2014-06-23 23:21 ` bug#17831: 24.4.50; bad default value for `Man-width' Leo Liu
-- strict thread matches above, loose matches on Subject: below --
2014-06-19 6:57 bug#17809: 24.4.50; Completions display Juri Linkov
2014-06-23 23:53 ` Juri Linkov
2014-10-05 22:02 ` Juri Linkov
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=53AA7222.1010905@gmx.at \
--to=rudalics@gmx.at \
--cc=17809@debbugs.gnu.org \
--cc=juri@jurta.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).