unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Antipov <dmantipov@yandex.ru>
To: Jan Tatarik <jan.tatarik@gmail.com>
Cc: 17609@debbugs.gnu.org
Subject: bug#17609: 24.4.50; trunk r117096: disappearing cursor in X
Date: Tue, 03 Jun 2014 16:40:22 +0400	[thread overview]
Message-ID: <538DC236.4000001@yandex.ru> (raw)
In-Reply-To: <87ppirqvlb.fsf@nb-jtatarik2.xing.hh>

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

On 06/02/2014 03:47 PM, Jan Tatarik wrote:

> There's still an issue. Pop-up notifications (notifications.el)
> triggered by emacs make the cursor disappear. The cursor remains hidden
> until emacs gets focus again.

I'm not familiar with this code and don't know how the notifications popup
window is created. Anyway, please try this tiny patch.

Dmitry



[-- Attachment #2: bug17609_2.patch --]
[-- Type: text/x-patch, Size: 546 bytes --]

=== modified file 'src/menu.c'
--- src/menu.c	2014-06-02 18:01:21 +0000
+++ src/menu.c	2014-06-03 12:29:28 +0000
@@ -1558,6 +1558,12 @@
      string contents, because Fredisplay may GC and relocate them.  */
   Fredisplay (Qt);
 
+#ifdef HAVE_X_WINDOWS
+  /* Don't confuse user with invisible cursor.  */
+  if (FRAME_X_P (f) && f->pointer_invisible)
+    FRAME_DISPLAY_INFO (f)->toggle_visible_pointer (f, 0);
+#endif
+
 #if defined USE_X_TOOLKIT || defined USE_GTK
   if (FRAME_WINDOW_P (f))
     return xw_popup_dialog (f, header, contents);


  reply	other threads:[~2014-06-03 12:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-27 13:43 bug#17609: 24.4.50; trunk r117096: disappearing cursor in X Jan Tatarik
2014-05-27 17:52 ` Dmitry Antipov
2014-05-27 20:16   ` Jan Tatarik
2014-05-27 23:30     ` Stefan Monnier
2014-05-28  4:17     ` Dmitry Antipov
2014-05-28  7:44       ` Jan Tatarik
2014-06-02 11:47       ` Jan Tatarik
2014-06-03 12:40         ` Dmitry Antipov [this message]
2014-06-05 20:42           ` Stefan Monnier
2020-09-09 11:59           ` Lars Ingebrigtsen
2020-12-06 15:56             ` Lars Ingebrigtsen

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=538DC236.4000001@yandex.ru \
    --to=dmantipov@yandex.ru \
    --cc=17609@debbugs.gnu.org \
    --cc=jan.tatarik@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).