From: the_wurfkreuz via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75093@debbugs.gnu.org
Subject: bug#75093: 31.0.50; Incorrent pointer position with minibuffer messages
Date: Thu, 26 Dec 2024 08:57:28 +0000 [thread overview]
Message-ID: <np9RfKHBeRgtpewhdT1O0izhyxI9Tpw4StjRE6Ou3zZE-T7f-FCjAY2DdaijP9ZQfGaxkvj3UkW4OZSrprzg9USzNXV9u_pRaIZ4Do3Qcx0=@proton.me> (raw)
In-Reply-To: <86wmfnyob3.fsf@gnu.org>
If my memory is not making things up right now, there might be situations where these kind of messages appear at the same time as you type. Which leads to a situation where characters are typed not at the current visual position of the cursor.
But i don't remember how exactly to reproduce this.
Sent with Proton Mail secure email.
On Thursday, December 26th, 2024 at 9:02, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Wed, 25 Dec 2024 19:23:44 +0000
> > From: the_wurfkreuz via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> >
> > If i don't have icomplete-vertical-mode enabled, i get minibuffer messages after the pointer:
> >
> > But if i enable it:
> >
> > (icomplete-vertical-mode)
> > (setq icomplete-compute-delay 0)
> > (setq icomplete-show-matches-on-no-input t)
> > Then the pointer will be after a minibuffer message:
>
>
> I think this is because we cannot display the minibuffer messages at
> the end of the minibuffer contents (which is not visible) in the
> vertical case.
>
> Why is it a problem where we show the cursor in these cases? What is
> important is that the minibuffer message be visible and does not
> interfere with typing at the minibuffer prompt.
prev parent reply other threads:[~2024-12-26 8:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 19:23 bug#75093: 31.0.50; Incorrent pointer position with minibuffer messages the_wurfkreuz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-26 6:02 ` Eli Zaretskii
2024-12-26 8:57 ` the_wurfkreuz via Bug reports for GNU Emacs, the Swiss army knife of text editors [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='np9RfKHBeRgtpewhdT1O0izhyxI9Tpw4StjRE6Ou3zZE-T7f-FCjAY2DdaijP9ZQfGaxkvj3UkW4OZSrprzg9USzNXV9u_pRaIZ4Do3Qcx0=@proton.me' \
--to=bug-gnu-emacs@gnu.org \
--cc=75093@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=the_wurfkreuz@proton.me \
/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.