unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jared Finder 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: gerd.moellmann@gmail.com, rpluim@gmail.com,
	stephen.berman@gmx.net, 74220@debbugs.gnu.org,
	ampinkas@gmail.com
Subject: bug#74220: invisible cursor
Date: Sat, 07 Dec 2024 11:14:46 -0800	[thread overview]
Message-ID: <b9be40ff4a33ac327ace9baf28ce4010@finder.org> (raw)
In-Reply-To: <86r06jisd7.fsf@gnu.org>

On 2024-12-07 04:34, Eli Zaretskii wrote:
>> Cc: gerd.moellmann@gmail.com, rpluim@gmail.com, 
>> stephen.berman@gmx.net,
>>  74220@debbugs.gnu.org, ampinkas@gmail.com
>> Date: Sat, 30 Nov 2024 09:08:06 +0200
>> From: Eli Zaretskii <eliz@gnu.org>
>> 
>> > Date: Fri, 29 Nov 2024 11:12:39 -0800
>> > From: Jared Finder <jared@finder.org>
>> > Cc: stephen.berman@gmx.net, rpluim@gmail.com, gerd.moellmann@gmail.com,
>> >  74220@debbugs.gnu.org, ampinkas@gmail.com
>> >
>> > I think Emacs is a special snowflake in that it doesn't (possibly
>> > can't?) rely on the GPM daemon drawing the mouse pointer. I did not see
>> > any other app with this problem. I tested Vim, Midnight Commander, Nano,
>> > and Bash. I don't know what is special about Emacs here. Perhaps the
>> > character under the mouse pointer is treated special in redisplay? Not
>> > sure.
>> 
>> Emacs needs to know where the mouse pointer is, and the rest it can
>> figure out by itself.  So if the GPM daemon drawing the mouse pointer
>> allows to know the pointer coordinates in a way that can be correlated
>> with the rows and column of the console, we should be okay.
>> 
>> Maybe when the GPM support for Emacs was written, the daemon couldn't
>> be used for drawing the pointer?
>> 
>> Anyway, one way to try to solve this is to try to use the
>> daemon-drawing of the mouse pointer.
>> 
>> > I will reach out to the kernel mailing list and see if they are ok
>> > relaxing the check and fixing this on their end.
>> 
>> Thanks.
> 
> Any progress here?

People on the Linux kernel mailing list agree this is a regression on 
Linux and that my suggested fix is probably appropriate. Tracking page: 
https://linux-regtracking.leemhuis.info/regzbot/regression/lore/CAG48ez0vg9W=oatvEqxvTSYNUx7htY23LxPrYCiuLZhZQuaGjg@mail.gmail.com/

   -- MJF





  reply	other threads:[~2024-12-07 19:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 20:06 bug#74220: invisible cursor Avraham Pinkas
2024-11-06 12:37 ` Eli Zaretskii
2024-11-06 13:55   ` Robert Pluim
2024-11-06 14:03     ` Gerd Möllmann
2024-11-06 14:22   ` jared via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 15:38     ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-06 16:17       ` Stephen Berman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-18  1:37         ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28  3:13           ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28 18:21             ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-28 20:20               ` Eli Zaretskii
2024-11-28 21:45                 ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-29  7:32                   ` Eli Zaretskii
2024-11-29 19:12                     ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30  7:08                       ` Eli Zaretskii
2024-12-07 12:34                         ` Eli Zaretskii
2024-12-07 19:14                           ` Jared Finder via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-12-07 19:29                             ` Eli Zaretskii

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=b9be40ff4a33ac327ace9baf28ce4010@finder.org \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74220@debbugs.gnu.org \
    --cc=ampinkas@gmail.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=jared@finder.org \
    --cc=rpluim@gmail.com \
    --cc=stephen.berman@gmx.net \
    /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).