From: Lars Ingebrigtsen <larsi@gnus.org>
To: mail@andy.glew.ca
Cc: 11993@debbugs.gnu.org
Subject: bug#11993: Emacs frames on other display hang during recursive edit on a different display
Date: Mon, 07 Dec 2020 18:10:34 +0100 [thread overview]
Message-ID: <87v9ddczjp.fsf@gnus.org> (raw)
In-Reply-To: <CAFjhD7L4J0k7v_yBW5QnfP4OMotCF874F877SH9D8hDTFhtALw@mail.gmail.com> (mail@andy.glew.ca's message of "Wed, 18 Jul 2012 20:34:19 -0700")
mail@andy.glew.ca writes:
> Please describe exactly what actions triggered the bug, and
> the precise symptoms of the bug. If you can, give a recipe
> starting from `emacs -Q':
>
> emacs -Q
>
> ...opens a frame (X Window)
>
> ...select that window, use it a bit to see that all works
>
> ESC-X make-frame-on-display
>
> ... type in display name
> ... note: in may case, the display is a different VNC session
>
> ... switch to the just opened emacs frame in that display, use it a bit
> to see that all works
>
> ... switch back, again, just to see that all works.
>
> ... in eother of the frames, type
>
> ESC-X recursive-edit
>
> ... I am still able to work in the frame that initiated the recursive
> edit.
>
> ... However, in the other frames of the emacs, while I can select the
> frame (X Window), and the cursor changes from outline to filled, I
> cannot do anything useful. The other frame(s) are hung: typing is not
> accepted, mouse clicks do not move the cursor.
(This bug report unfortunately got no response at the time.)
I wasn't able to follow the recipe (because I don't use VNC), but I
can't talk about similar bugs in the recent past. Are you still seeing
this issue in more recent versions of Emacs?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-07 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 3:34 bug#11993: Emacs frames on other display hang during recursive edit on a different display mail
2020-12-07 17:10 ` Lars Ingebrigtsen [this message]
2021-01-20 17:07 ` 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=87v9ddczjp.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=11993@debbugs.gnu.org \
--cc=mail@andy.glew.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).