unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bob Rogers <rogers@rgrjr.com>
Cc: 57468@debbugs.gnu.org, larsi@gnus.org
Subject: bug#57468: 29.0.50; Text cursor continues to blink when frame loses focus
Date: Wed, 31 Aug 2022 22:24:38 +0300	[thread overview]
Message-ID: <83edwwrzbd.fsf@gnu.org> (raw)
In-Reply-To: <25359.45100.999353.785164@orion.rgrjr.com> (message from Bob Rogers on Wed, 31 Aug 2022 12:02:04 -0700)

> From: Bob Rogers <rogers@rgrjr.com>
> Date: Wed, 31 Aug 2022 12:02:04 -0700
> CC: Eli Zaretskii <eliz@gnu.org>, 57468@debbugs.gnu.org
> 
>    From: Lars Ingebrigtsen <larsi@gnus.org>
>    Date: Wed, 31 Aug 2022 12:03:38 +0200
> 
>    Bob Rogers <rogers@rgrjr.com> writes:
> 
>    >    Then I brought up a pre-existing emacs instance running as root
>    > (which I had forgotten about) and found that its blinking cursor stays
>    > on persistently, and the focus in/out code above shows that it's getting
>    > neither event.
> 
>    How was the root Emacs started?  Could it be in a way that stops the
>    window manager from delivering events to it?
> 
> Just "emacs &" after "su" in a shell.  I should emphasize that I've seen
> nothing special about the root emacs; all instances save one switched
> between working and nonworking at long but unpredictable intervals.  And
> the other problematic instances were also spawned from shells, though
> some were from a Konsole shell, some were via ssh with tunneled X11, and
> some from an emacs shell window.

I guess the next step is to set a breakpoint in every place where we
call x_focus_changed, and see whether the X events are delivered to
Emacs in the "su" Emacs.  If the events aren't delivered, this is not
an Emacs problem.





  reply	other threads:[~2022-08-31 19:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-28 23:38 bug#57468: 29.0.50; Text cursor continues to blink when frame loses focus Bob Rogers
2022-08-29 15:21 ` Lars Ingebrigtsen
2022-08-29 18:04   ` Bob Rogers
2022-08-30 10:27     ` Lars Ingebrigtsen
2022-08-30 12:02       ` Eli Zaretskii
2022-08-30 23:33         ` Bob Rogers
2022-08-31 10:03           ` Lars Ingebrigtsen
2022-08-31 19:02             ` Bob Rogers
2022-08-31 19:24               ` Eli Zaretskii [this message]
2022-08-31 19:31               ` Bob Rogers
2022-09-03  9:44                 ` Lars Ingebrigtsen
2022-09-03 11:23                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 11:52                     ` Lars Ingebrigtsen
2022-09-03 11:56                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 12:08                         ` Lars Ingebrigtsen
2022-09-03 12:26                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 12:37                             ` Lars Ingebrigtsen
2022-09-03 13:03                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 13:44                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 13:47                                 ` Lars Ingebrigtsen
2022-09-03 13:54                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 17:53                                     ` Bob Rogers
2022-09-04  0:36                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=83edwwrzbd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57468@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=rogers@rgrjr.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).