From: Philip Kaludercic <philipk@posteo.net>
To: Ergus <spacibba@aol.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Set max size for *Completions*
Date: Mon, 07 Mar 2022 15:17:45 +0000 [thread overview]
Message-ID: <87sfrtaj1i.fsf@posteo.net> (raw)
In-Reply-To: <8735jtn6ug.fsf@aol.com> (Ergus's message of "Mon, 7 Mar 2022 16:02:57 +0100")
Ergus <spacibba@aol.com> writes:
> Hi:
>
> Do we have any way to specify a max size/height for the *Completions*
> window??
One way it to enable temp-buffer-resize-mode and then set
temp-buffer-max-height to whatever size you want. This might have the
unintended side effect that other windows are also affected. I manged
to solve this by setting temp-buffer-max-height to a function:
(lambda (buf)
(if (string-match-p
(rx bos (or "*Completions*") eos)
(buffer-name buf))
10 (window-height)))
--
Philip Kaludercic
next prev parent reply other threads:[~2022-03-07 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8735jtn6ug.fsf.ref@aol.com>
2022-03-07 15:02 ` Set max size for *Completions* Ergus
2022-03-07 15:17 ` Philip Kaludercic [this message]
2022-03-07 20:50 ` Ergus
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=87sfrtaj1i.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=help-gnu-emacs@gnu.org \
--cc=spacibba@aol.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.
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).