From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: lorentey@elte.hu (=?iso-8859-2?Q?L=F5rentey_K=E1roly?=) Newsgroups: gmane.emacs.devel,gmane.emacs.multi-tty,gmane.emacs.multi-tty Subject: Re: Emacs routinely gets stuck in single_kboard mode Date: Mon, 12 Jul 2004 08:18:15 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1089613140 32377 80.91.224.253 (12 Jul 2004 06:19:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Jul 2004 06:19:00 +0000 (UTC) Cc: multi-tty@lists.fnord.hu, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jul 12 08:18:53 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Bju9N-0000Qx-00 for ; Mon, 12 Jul 2004 08:18:53 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Bju9N-0002lu-00 for ; Mon, 12 Jul 2004 08:18:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BjuBg-0004pM-Ba for emacs-devel@quimby.gnus.org; Mon, 12 Jul 2004 02:21:16 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BjuBc-0004pG-QJ for emacs-devel@gnu.org; Mon, 12 Jul 2004 02:21:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BjuBb-0004p4-VP for emacs-devel@gnu.org; Mon, 12 Jul 2004 02:21:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BjuBb-0004p1-Sr for emacs-devel@gnu.org; Mon, 12 Jul 2004 02:21:11 -0400 Original-Received: from [157.181.151.9] (helo=mx2.elte.hu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Bju9D-0000Od-Ui for emacs-devel@gnu.org; Mon, 12 Jul 2004 02:18:44 -0400 Original-Received: from mailbox1.caesar.elte.hu (mailbox1.caesar.elte.hu [157.181.151.157]) by mx2.elte.hu (Postfix) with ESMTP id BE0C215F99E; Mon, 12 Jul 2004 08:15:04 +0200 (CEST) Original-Received: from eris (line-73-204.dial.freestart.hu [213.197.73.204]) by mailbox1.caesar.elte.hu (Postfix) with ESMTP id 046D4A00E509; Mon, 12 Jul 2004 08:18:25 +0200 (CEST) Original-Received: by eris (Postfix, from userid 1000) id 872DC47D01; Mon, 12 Jul 2004 08:18:15 +0200 (CEST) Original-To: multi-tty@lists.fnord.hu In-Reply-To: (Richard Stallman's message of "Sun, 11 Jul 2004 19:23:37 -0400") User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=0.098, required 5.9, BAYES_00 -4.90, RCVD_IN_DYNABLOCK 2.60, WORK_AT_HOME 2.40 X-ELTE-SpamLevel: X-ELTE-SpamScore: 0 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: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:25603 gmane.emacs.multi-tty:23 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:25603 Richard Stallman writes: > > A recursive edit or debug session must set single_kboard, > > because the environment of the recursive edit or debug session > > would otherwise be imposed on all the other terminals. > > I see, but if there are multiple frames, then that recursive > environment is imposed on them, and AFAICS in that case this only > results in some small inconveniences that are easy to work around. > > Sorry, I don't follow what you're saying here. > The other terminals won't see the buffer that the recursive > edit or debug session is in, and there is potential > for a lot of confusion. I agree, but I think locking up the other displays leads to even more problems. Having a debug window hidden on another display (or while we are at it, on another frame) is confusing, but at least I can use C-M-c or C-] to return to sanity from everywhere. On the other hand, having a whole display completely locked up with no indication of what happened, and no way to unlock without switching to another display is guaranteed to confuse and annoy me. Here is an example: Let's say I log in to my office workstation from home, and start up an Emacs display on my remote X server via emacsclient. Suppose that I was careless, and before I went home I somehow left my Emacs inside a recursive edit. In this case, emacsclient will succeed to create a new frame on the remote server, but the frame will not accept any input, not even a delete-frame event from the window manager, until I go back to my office to press C-]. :-( --=20 K=E1roly