GNU bug report logs - #16479
24.3.50; daemon freeze with tty menus

Previous Next

Package: emacs;

Reported by: Mark Oteiza <mvoteiza <at> udel.edu>

Date: Fri, 17 Jan 2014 09:40:02 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3.50

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #44 received at 16479 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: mvoteiza <at> udel.edu, 16479 <at> debbugs.gnu.org
Subject: Re: bug#16479: 24.3.50; daemon freeze with tty menus
Date: Mon, 20 Jan 2014 23:17:03 +0200
> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: mvoteiza <at> udel.edu,  16479 <at> debbugs.gnu.org
> Date: Mon, 20 Jan 2014 15:28:42 -0500
> 
> >> 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.

OK, then I know what to do.  Thanks.




This bug report was last modified 3 years and 86 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.