From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.multi-tty,gmane.emacs.devel Subject: Re: Emacs routinely gets stuck in single_kboard mode Date: Mon, 12 Jul 2004 19:57:14 -0400 Sender: multi-tty-bounces@lists.fnord.hu Message-ID: References: Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1089676669 15782 80.91.224.253 (12 Jul 2004 23:57:49 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Jul 2004 23:57:49 +0000 (UTC) Cc: multi-tty@lists.fnord.hu, emacs-devel@gnu.org Original-X-From: multi-tty-bounces@lists.fnord.hu Tue Jul 13 01:57:40 2004 Return-path: Original-Received: from ninsei.hu ([212.92.23.158] helo=chatsubo.ninsei.hu) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BkAfw-00005L-00 for ; Tue, 13 Jul 2004 01:57:40 +0200 Original-Received: from [127.0.0.1] (nixon [127.0.0.1]) by chatsubo.ninsei.hu (Postfix) with ESMTP id 117B21AC8F; Tue, 13 Jul 2004 01:57:29 +0200 (CEST) Original-Received: from fencepost.gnu.org (fencepost.gnu.org [199.232.76.164]) by chatsubo.ninsei.hu (Postfix) with ESMTP id 20BDA1AC8D for ; Tue, 13 Jul 2004 01:57:25 +0200 (CEST) Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BkAfa-0000id-RB; Mon, 12 Jul 2004 19:57:14 -0400 Original-To: lorentey@elte.hu (=?iso-8859-2?Q?L=F5rentey_K=E1roly?=) In-reply-to: X-BeenThere: multi-tty@lists.fnord.hu X-Mailman-Version: 2.1.4 Precedence: list List-Id: Discussions of multiple tty support in Emacs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: multi-tty-bounces@lists.fnord.hu Xref: main.gmane.org gmane.emacs.multi-tty:24 gmane.emacs.devel:25631 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:25631 > 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. Maybe it should display something saying "Locked by another keyboard" in all the windows for other keyboards. That way, the person at that keyboard will understand why it is locked. You seem to be envisioning that there is only one user, who uses the various different keyboards. I've always thought in terms of a different user at each keyboard. Perhaps this is why we have different ideas of what would be desirable.