unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: "Eli Zaretskii" <eliz@gnu.org>, "João Távora" <joaotavora@gmail.com>
Cc: 62816@debbugs.gnu.org
Subject: bug#62816: 30.0.50; ElDoc blinks echo area when eldoc-documentation-compose is used
Date: Sat, 15 Apr 2023 14:40:19 +0300	[thread overview]
Message-ID: <472de165-ea1b-817e-f8b6-d4b70e4e5613@gutov.dev> (raw)
In-Reply-To: <834jphecek.fsf@gnu.org>

On 15/04/2023 12:13, Eli Zaretskii wrote:
>> Right, exactly.  We were just talking about that.  This is not a
>> regression from Emacs 28 (I'm 99% sure).  It was already there.
>> But the bug is so-so-serious (somewhat annoying flickering, though
>> not in TTY frames).  The fix is simple enough (IMHO, of course,
>> because I wrote the code ... and the bug).
> What is the bug, exactly?  Is it just that the mini-window gets
> resized back and forth in some scenario?  Or is it something else?

Resized back and forth, and "blinks" with blank content after every user 
keypress. Which makes it quite annoying to use 
eldoc-documentation-compose in GUI Emacs.

The effect is only visual, though.





      parent reply	other threads:[~2023-04-15 11:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-13 14:47 bug#62816: 30.0.50; ElDoc blinks echo area when eldoc-documentation-compose is used João Távora
2023-04-13 22:58 ` Dmitry Gutov
2023-04-13 23:23   ` João Távora
2023-04-13 23:37     ` Dmitry Gutov
2023-04-14  0:16       ` João Távora
2023-04-14  0:22         ` Dmitry Gutov
2023-04-15  1:03           ` Dmitry Gutov
2023-04-14 18:03 ` Dmitry Gutov
2023-04-14 18:09   ` João Távora
2023-04-14 18:53     ` Eli Zaretskii
2023-04-14 19:58       ` João Távora
2023-04-15  9:13         ` Eli Zaretskii
2023-04-15 11:04           ` João Távora
2023-04-15 11:40           ` Dmitry Gutov [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

  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=472de165-ea1b-817e-f8b6-d4b70e4e5613@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=62816@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@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 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).