From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#74220: invisible cursor Date: Sat, 07 Dec 2024 14:34:44 +0200 Message-ID: <86r06jisd7.fsf@gnu.org> References: <87ldxwmppm.fsf@gmail.com> <86o72ssfm4.fsf@gnu.org> <87bjyscp5e.fsf@gmx.net> <2b5006ac22491fd8c509120ad653117d@finder.org> <8b70d54cd579f33d1e698a0f8927dc4f@finder.org> <865xo7cdpv.fsf@gnu.org> <86y112bim0.fsf@gnu.org> <889037a6131ad45d7e5dfb69e119c060@finder.org> <86a5dhb3mx.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20362"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gerd.moellmann@gmail.com, rpluim@gmail.com, stephen.berman@gmx.net, 74220@debbugs.gnu.org, ampinkas@gmail.com To: jared@finder.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Dec 07 13:35:11 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1tJu1f-00059H-9u for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 07 Dec 2024 13:35:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tJu1Z-0006VU-8A; Sat, 07 Dec 2024 07:35:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJu1X-0006VE-3J for bug-gnu-emacs@gnu.org; Sat, 07 Dec 2024 07:35:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1tJu1W-00039U-Q8 for bug-gnu-emacs@gnu.org; Sat, 07 Dec 2024 07:35:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debbugs.gnu.org; s=debbugs-gnu-org; h=References:In-Reply-To:From:Date:To:Subject; bh=MJisJAeckKD8+aM39Vh4FURBnGHZLOLP5yJM0cUkjQo=; b=bjJRPco3VTxZyEX87lfqJSXGM/uKyLZyGoGT1EKI7ZNsISGVv20D5Hoa6qQcmErWgI69eFGZUpEkMlNlsWX0Ail7fT1BDqUNS/3mC493jlES5UJvvW1uMf0RPrZgcezbqW/00d2cy+kJYmNhtpCXbD98xVrztyuYpCYnszXqWhJ90SelNIIvKrGisXFvfg26kDoiArJfdBojtwNWzXRqgn3QEVz2+OqcNDVF2uy9HT2Msfrj/gOU3D9KxsuPqt2Sm62jnX17TQDxaY/DriwNY7Dpgis6YZr1tI5ZuF1DppW/PIdDhCnEUawrO104x0+6Axa00zyPHy+RXlRSKUir5A==; Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1tJu1W-0002Od-JQ for bug-gnu-emacs@gnu.org; Sat, 07 Dec 2024 07:35:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 07 Dec 2024 12:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 74220 X-GNU-PR-Package: emacs Original-Received: via spool by 74220-submit@debbugs.gnu.org id=B74220.17335748959189 (code B ref 74220); Sat, 07 Dec 2024 12:35:02 +0000 Original-Received: (at 74220) by debbugs.gnu.org; 7 Dec 2024 12:34:55 +0000 Original-Received: from localhost ([127.0.0.1]:45827 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tJu1P-0002O8-3M for submit@debbugs.gnu.org; Sat, 07 Dec 2024 07:34:55 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40858) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1tJu1M-0002Nq-RP for 74220@debbugs.gnu.org; Sat, 07 Dec 2024 07:34:53 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tJu1H-000380-9B; Sat, 07 Dec 2024 07:34:47 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=MJisJAeckKD8+aM39Vh4FURBnGHZLOLP5yJM0cUkjQo=; b=cRC6tiSbMMHV fhV9Pl7eLDDf4cMBKb4ryNOOZHPoBH70DaibsWCyL1XWqmUnHaKY0vAU7QNsdk/vih8z6L4embUhb GLyRvRQESx8Ln7jCoqJZ4Cl+tOnn+TMSDf86s/WLsaxJq6Cy3Tny75ioH8ypWag4MpH/fOCCQfK/5 FkoT2Ikht3UnGbJaq53qg7wz2lO2PzaGt74IZHdqZmUHZp5adyYzZCzM3uG8vuEKhMAKxa52Lrpuv djYyRKeuR91Zl4iEfpX1wrm4Ydh+G5w2VhjWBGvdha2Ze7F6R8rlMgXoUiTebir283NP8iKAqj5gG NXTHfeYjbTX4zoBoK13fKQ==; In-Reply-To: <86a5dhb3mx.fsf@gnu.org> (message from Eli Zaretskii on Sat, 30 Nov 2024 09:08:06 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:296554 Archived-At: > 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 > > > Date: Fri, 29 Nov 2024 11:12:39 -0800 > > From: Jared Finder > > 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?