From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: poor handling of multiple C-g with multi-tty (apparent hangs) Date: Mon, 11 Aug 2008 11:56:48 -0700 Message-ID: <200808111856.m7BIumO3019150@sallyv1.ics.uci.edu> References: <87tzdr4fh6.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1218481828 18952 80.91.229.12 (11 Aug 2008 19:10:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 11 Aug 2008 19:10:28 +0000 (UTC) Cc: Ami Fischman , emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 11 21:11:19 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KScnL-0004xn-6d for ged-emacs-devel@m.gmane.org; Mon, 11 Aug 2008 21:11:07 +0200 Original-Received: from localhost ([127.0.0.1]:38681 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KScmP-000424-52 for ged-emacs-devel@m.gmane.org; Mon, 11 Aug 2008 15:10:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KScaf-0000fs-Aq for emacs-devel@gnu.org; Mon, 11 Aug 2008 14:58:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KScae-0000e5-8t for emacs-devel@gnu.org; Mon, 11 Aug 2008 14:58:00 -0400 Original-Received: from [199.232.76.173] (port=51565 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KScad-0000dk-L5 for emacs-devel@gnu.org; Mon, 11 Aug 2008 14:57:59 -0400 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]:61098) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1KScad-000224-7E for emacs-devel@gnu.org; Mon, 11 Aug 2008 14:57:59 -0400 X-ICS-MailScanner-Watermark: 1219085808.99706@zsyVBcOTc0YPWoEZEulIqQ Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m7BIumO3019150; Mon, 11 Aug 2008 11:56:48 -0700 (PDT) In-Reply-To: <87tzdr4fh6.fsf@stupidchicken.com> (Chong Yidong's message of "Mon, 11 Aug 2008 13:40:53 -0400") Original-Lines: 36 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:102293 Archived-At: Chong Yidong writes: > "Ami Fischman" writes: > > > Emacs has code to deal with C-g being entered while a quit is already > > in progress, meant to suspend emacs and drop the user to the superior > > shell or debugger (see section 59.7 Emergency Escape of the emacs > > info). This is done if emacs believes it's a good idea, which > > criteria includes "running in tty mode". Unfortunately this was never > > updated to work correctly with the multi-tty patch. > > Thanks for pointing this out. > > IIUC, the "emergency C-g" behavior is geared towards the traditional > setup where there's only one text-only terminal available. There, the > emergency C-g is the only way to drop back to the shell if Emacs gets > stuck. > > It's disabled for graphical terminals because there, you can open up a > separate terminal to kill/suspend the Emacs process. > > This implies that we should disable the emergency C-g if Emacs is > running on more than one terminal, as in the following patch. Does this do TRT given this scenario: ssh into a machine enacs -nw -f server-start then go to the console of that machine and do: emacsclient -t assume there's no other console and no other network connection. If emacs gets stuck, can you still do C-g ?