From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Eli Zaretskii <eliz@gnu.org>
Cc: 24293@debbugs.gnu.org
Subject: bug#24293: 25.1; Display bug: icomplete prompt not visible with icomplete-separator "\n"
Date: Tue, 23 Aug 2016 12:38:00 -0700 (PDT) [thread overview]
Message-ID: <7b8693c3-815c-4a07-9031-d71ab2ea9391@default> (raw)
In-Reply-To: <87fupvxq3g.fsf@web.de>
> Maybe we can fix it in icomplete instead. AFAIK icomplete tries to
> limit the number of shown candidates according to some settings like
> maximum number of lines to display, but doesn't handle the case of a
> separator including a newline character correctly.
>
> Is it possible to determine reliably the number of lines a minibuffer
> window can display maximally for given max-mini-window-height?
1. Please take care not to break the case of a standalone minibuffer
frame, or any other context where the minibuffer can be resized to
accommodate a large number of icomplete candidates.
IOW, a newline separator is not a problem at all in some contexts.
Please don't limit or break that behavior. Thx.
2. It's not clear to me why this should be handled in icomplete.el.
Doesn't the same problem arise if multi-line text is inserted in
the minibuffer or if any other program does something similar to
what icomplete does? IOW, isn't it a general problem, which would
call for a general solution?
next prev parent reply other threads:[~2016-08-23 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 15:44 bug#24293: 25.1; Display bug: icomplete prompt not visible with icomplete-separator "\n" Michael Heerdegen
2016-08-23 16:18 ` Eli Zaretskii
2016-08-23 19:06 ` Michael Heerdegen
2016-08-23 19:38 ` Drew Adams [this message]
2016-08-24 2:44 ` Eli Zaretskii
2016-08-24 2:47 ` Eli Zaretskii
2016-08-24 9:08 ` martin rudalics
2020-09-19 17:47 ` Stefan Monnier
2020-04-05 12:42 ` Dmitry Gutov
2020-04-05 12:56 ` Dmitry Gutov
2020-12-04 11:08 ` Lars Ingebrigtsen
2020-12-08 0:08 ` Michael Heerdegen
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=7b8693c3-815c-4a07-9031-d71ab2ea9391@default \
--to=drew.adams@oracle.com \
--cc=24293@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
/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).