all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Madhu <enometh@meer.net>
Cc: 59733@debbugs.gnu.org
Subject: bug#59733: 29.0.50; unrespnsive Xaw menus
Date: Sun, 04 Dec 2022 14:36:59 +0800	[thread overview]
Message-ID: <87mt83r7xw.fsf@yahoo.com> (raw)
In-Reply-To: <20221204.105422.2186177425946290377.enometh@meer.net> (Madhu's message of "Sun, 04 Dec 2022 10:54:22 +0530 (IST)")

Madhu <enometh@meer.net> writes:

> [Maybe this can be done on the same machine with xpra. Right now I'm
> set up walking between two rooms...  it's tricky as the frame display
> can lock up and the process has to be killed.]

You're welcome to try, but my gut feeling is that it won't work.  Thanks
for going through all that trouble to debug this!

> The upshot is XtGrabPointer returns 0 and the menu becomes unresponsive[1]
>
> When it works, i.e. when XtGrabPointer returns True, It seems I'm not
> able to step into XtGrabPointer as `s' puts me on the next line of
> pop_up_menu.

If XtGrabPointer returns a non-zero value, then it means obtaining the
grab failed.  Exactly which non-zero value does it return?  Do the menus
start working if you comment out the call to "XtGrabPointer" entirely?

The relevant return codes are:

        #define GrabSuccess		0
        #define AlreadyGrabbed		1
        #define GrabInvalidTime		2
        #define GrabNotViewable		3
        #define GrabFrozen		4

> PS (can the typo in the Subject line be fixed)

Yes, as long as you keep the "bug#" intact.





  reply	other threads:[~2022-12-04  6:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  2:35 bug#59733: 29.0.50; unrespnsive Xaw menus Madhu
2022-12-01  7:17 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01  9:34   ` Madhu
2022-12-01 10:10     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 12:56       ` Madhu
2022-12-01 13:11         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 13:55           ` Visuwesh
2022-12-01 14:24           ` Madhu
2022-12-02  1:04             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04  5:24               ` Madhu
2022-12-04  6:36                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-05  8:05                   ` bug#59733: 29.0.50; unresponsive " Madhu
2022-12-05  8:58                     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mt83r7xw.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=59733@debbugs.gnu.org \
    --cc=enometh@meer.net \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.