From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: ynyaaa@gmail.com, 38645-done@debbugs.gnu.org
Subject: bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown
Date: Mon, 30 Dec 2019 18:07:02 +0200 [thread overview]
Message-ID: <83a779n6ft.fsf@gnu.org> (raw)
In-Reply-To: <0c0413bd-b701-c23c-4a13-7e9ea11b8153@gmx.at> (message from martin rudalics on Sun, 29 Dec 2019 20:30:47 +0100)
> Cc: ynyaaa@gmail.com, 38645@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Sun, 29 Dec 2019 20:30:47 +0100
>
> >> Did you check whether any of the
> >> other clear_message calls would need a similar treatment?
> >
> > Which ones?
>
> Maybe the last one in read_char itself. But I don't understand well what
> we are doing there.
We are evidently clearing the echo area if the input method left
something there. But I couldn't create a situation where there was
anything left to do after the input method finished its job, not by
turning on an input method in the active minibuffer. Quail has its
own ideas about handling this situation; see quail-minibuffer-message
and quail-show-guidance. In particular, it arranges for the guidance
to appear on the second line of the mini-window (the first one being
where you type at the prompt), and never shows more than one line of
candidates for input there (you need to scroll with up- and
down-arrows). And when input is done, the mini-window resizes back.
So if someone knows how to trigger a mini-window resizing problems
related to input methods, please show a recipe (and reopen the bug).
Meanwhile, I've installed the fix and I'm closing this bug report.
Thanks for the feedback.
prev parent reply other threads:[~2019-12-30 16:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 6:49 bug#38645: 26.3; minibuffer input is called with multi-line window when multi-line message is shown ynyaaa
2019-12-17 7:41 ` Eli Zaretskii
2019-12-17 11:55 ` ynyaaa
2019-12-17 12:07 ` Eli Zaretskii
2019-12-18 10:52 ` ynyaaa
2019-12-18 16:31 ` Eli Zaretskii
2019-12-20 2:16 ` ynyaaa
2019-12-26 20:49 ` Eli Zaretskii
2019-12-27 9:12 ` martin rudalics
2019-12-27 9:21 ` Eli Zaretskii
2019-12-27 9:46 ` martin rudalics
2019-12-27 10:29 ` Eli Zaretskii
2019-12-29 14:15 ` Eli Zaretskii
2019-12-29 18:33 ` martin rudalics
2019-12-29 18:50 ` Eli Zaretskii
2019-12-29 19:30 ` martin rudalics
2019-12-30 16:07 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a779n6ft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38645-done@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=ynyaaa@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.