unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mvoteiza@udel.edu, 16479@debbugs.gnu.org
Subject: bug#16479: 24.3.50; daemon freeze with tty menus
Date: Mon, 20 Jan 2014 15:28:42 -0500	[thread overview]
Message-ID: <jwvmwiq5rij.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83y52ah2f9.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Jan 2014 21:35:22 +0200")

>> Whatever we do, we should do it whether or not a tty menu is displayed.
>> Switching frame inside a process filter is nasty but allowed.  So:
>> - server.el should probably only change the selected frame temporarily and
>> revert it before returning from the process filter.
> But I think server.el does this on purpose: if it didn't switch to the
> new frame, you couldn't start typing into it after invoking
> emacsclient, even when there's no menu displayed.  Wouldn't that be
> confusing?

I'm not sure it's the case.  The reason is that you're talking about
a change of focus whereas the code changed the selected frame.  The two
are related but the relation is very murky.

> Does the fact that you type into one frame and get response in another
> count as "a bit strangely"?

Yes.


        Stefan





  reply	other threads:[~2014-01-20 20:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17  9:39 bug#16479: 24.3.50; daemon freeze with tty menus Mark Oteiza
2014-01-17  9:55 ` Eli Zaretskii
2014-01-17 10:21   ` Mark Oteiza
2014-01-17 11:10     ` Eli Zaretskii
2014-01-17 11:59       ` Eli Zaretskii
2014-01-17 14:55         ` Stefan Monnier
2014-01-17 15:26           ` Eli Zaretskii
2014-01-17 16:16             ` Stefan Monnier
2014-01-17 18:54               ` Eli Zaretskii
2014-01-20 17:48                 ` Eli Zaretskii
2014-01-20 18:27                   ` Stefan Monnier
2014-01-20 19:35                     ` Eli Zaretskii
2014-01-20 20:28                       ` Stefan Monnier [this message]
2014-01-20 21:17                         ` Eli Zaretskii
2014-01-25  9:59                           ` Eli Zaretskii
2014-01-25 22:39                             ` Stefan Monnier
2014-01-26  3:52                               ` Eli Zaretskii
2014-01-26  6:17                                 ` Stefan Monnier
2014-01-26 16:23                                   ` Eli Zaretskii
2014-01-27  2:07                                     ` Stefan Monnier
2014-02-01  9:43                                       ` Eli Zaretskii
2014-02-02  1:27                                         ` Stefan Monnier
2022-04-23 14:09 ` Lars Ingebrigtsen
2022-04-24 19:28   ` Mark Oteiza
2022-04-24 19:45     ` 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=jwvmwiq5rij.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=16479@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=mvoteiza@udel.edu \
    /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).