unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Burns <bburns.km@gmail.com>
To: Joseph Mingrone <jrm@ftfl.ca>
Cc: 22214@debbugs.gnu.org
Subject: bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode
Date: Thu, 24 Dec 2015 01:43:39 -0600	[thread overview]
Message-ID: <CA+XjW6y+5RARgBd9jUhMzSMwyv1TJugtRDA7-yiPq_nouTL7Rw@mail.gmail.com> (raw)
In-Reply-To: <861tacamk1.fsf@phe.ftfl.ca>

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

Joseph Mingrone <jrm@ftfl.ca> wrote:

> Here is the simplest example I can come up with that causes the problem.
>
> ;; substitute x-get-selection-value for 24.x
> (run-at-time nil 2 (gui-get-primary-selection))
> (menu-set-font)
>

Thanks, that does it - I tried adding menu-or-popup-active-p around it but
it didn't help -

(defun foo ()
  (if (not (menu-or-popup-active-p))
    (x-get-selection-value)))

(run-at-time nil 2 'foo)
(menu-set-font)

Maybe there's some other way to tell if a gui window is showing / waiting
for input? Then as a workaround I could just skip checking the clipboard.

I looked at some of the internals - as Eli said there's an event loop for
the x dialog that also checks the existing Emacs timers, which in this case
would be checking the x selection and starting another timer.

I'm not sure why that would cause a hang though, if the x selection returns
immediately.

Thanks again for your help in tracking this down - I'll keep tracing
through the code to see if I can figure out what's going on, and why
menu-or-popup-active-p doesn't help.

Brian

[-- Attachment #2: Type: text/html, Size: 1680 bytes --]

  reply	other threads:[~2015-12-24  7:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-20  6:26 bug#22214: 25.0.50; lock up with gui dialogs and clipmon-mode Joseph Mingrone
2015-12-20 15:54 ` Eli Zaretskii
2015-12-21  2:31   ` Joseph Mingrone
2015-12-21 15:24     ` Eli Zaretskii
2015-12-21 16:41       ` Joseph Mingrone
2015-12-21 17:50         ` Eli Zaretskii
2015-12-21 19:42           ` Joseph Mingrone
2015-12-21  0:21 ` Brian Burns
2015-12-21  0:45   ` Joseph Mingrone
2015-12-22  7:56     ` Brian Burns
2015-12-21 15:26   ` Eli Zaretskii
2015-12-22  5:21 ` Joseph Mingrone
2015-12-22 16:06   ` Eli Zaretskii
2015-12-23 17:00     ` Joseph Mingrone
2015-12-23 17:12       ` Eli Zaretskii
2015-12-23 18:18         ` Joseph Mingrone
2015-12-23 18:22           ` Eli Zaretskii
2015-12-23 20:16             ` Brian Burns
2015-12-23 21:21               ` Joseph Mingrone
2015-12-24  7:43                 ` Brian Burns [this message]
2015-12-24 16:20                   ` Eli Zaretskii
2015-12-27  7:29                     ` Brian Burns
2022-04-23 14:06                 ` Lars Ingebrigtsen
2022-04-24 13:23                   ` Joseph Mingrone
2022-04-25  0:50                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23  8:02                       ` Lars Ingebrigtsen
2022-05-23 19:02                         ` Joseph Mingrone
2022-05-24  0:27                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-29 15:51                             ` Joseph Mingrone
2022-05-29 23:58                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30  6:05                               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-30 13:00                                 ` Joseph Mingrone
2022-05-30 13:34                                   ` 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=CA+XjW6y+5RARgBd9jUhMzSMwyv1TJugtRDA7-yiPq_nouTL7Rw@mail.gmail.com \
    --to=bburns.km@gmail.com \
    --cc=22214@debbugs.gnu.org \
    --cc=jrm@ftfl.ca \
    /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).