unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: 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 21:06:11 +0200	[thread overview]
Message-ID: <87fupvxq3g.fsf@web.de> (raw)
In-Reply-To: <83d1kzfogn.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Aug 2016 19:18:48 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> What happens next is that the after-string causes the display to start
> at the beginning of the string, because Emacs cannot start the
> window's display in the middle of an overlay string.  So what is
> actually shown is not the end, but the middle of the overlay string.

Ok, it's probably not worth trying to change the display engine for
this.

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?


Michael.





  reply	other threads:[~2016-08-23 19:06 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 [this message]
2016-08-23 19:38     ` Drew Adams
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=87fupvxq3g.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=24293@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).