From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: emacsclient bug Date: Thu, 17 Jan 2008 13:42:20 -0500 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1200595395 22511 80.91.229.12 (17 Jan 2008 18:43:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 17 Jan 2008 18:43:15 +0000 (UTC) Cc: emacs-devel@gnu.org To: Len Trigg Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 17 19:43:32 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 1JFZi8-00041T-F5 for ged-emacs-devel@m.gmane.org; Thu, 17 Jan 2008 19:43:32 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JFZhi-0000sz-Qh for ged-emacs-devel@m.gmane.org; Thu, 17 Jan 2008 13:43:06 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JFZh8-0000iI-6J for emacs-devel@gnu.org; Thu, 17 Jan 2008 13:42:30 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JFZh5-0000gX-4K for emacs-devel@gnu.org; Thu, 17 Jan 2008 13:42:29 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JFZh4-0000gP-V1 for emacs-devel@gnu.org; Thu, 17 Jan 2008 13:42:26 -0500 Original-Received: from mercure.iro.umontreal.ca ([132.204.24.67]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JFZh4-0001XZ-Is for emacs-devel@gnu.org; Thu, 17 Jan 2008 13:42:26 -0500 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 4F5162CF6F3; Thu, 17 Jan 2008 13:42:26 -0500 (EST) Original-Received: from faina.iro.umontreal.ca (faina.iro.umontreal.ca [132.204.26.177]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 369FF3FE0; Thu, 17 Jan 2008 13:42:20 -0500 (EST) Original-Received: by faina.iro.umontreal.ca (Postfix, from userid 20848) id 205916CAB5; Thu, 17 Jan 2008 13:42:20 -0500 (EST) In-Reply-To: (Len Trigg's message of "Fri, 18 Jan 2008 06:56:19 +1300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-2.82, requis 5, autolearn=not spam, ALL_TRUSTED -2.82) X-DIRO-MailScanner-From: monnier@iro.umontreal.ca X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) 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:87030 Archived-At: >> > I use emacs pretty much exclusively in multi-tty mode, seldom creating >> > actual X frames. I recently switched from the pre-emacs-22 multi-tty >> > branch to the new emacs-23 snapshot (from a few days ago) and have >> > noticed some changes. >> >> > 1) Start a new emacs in a tty >> >> > 2) (server-start) >> >> > 3) In another shell, do: >> > $ emacsclient >> >> > 4) BUG: emacs opens a new frame. It should instead load into my >> > existing emacs tty. The old multi-tty emacsclient did this correctly >> >> This is not a bug: the behavior was chosen to better match the previous >> non-multi-tty behavior. You need to add the "-t" argument to tell >> emacsclient to open a new frame in the local tty. > I should add that I think the bug is only after freshly invoking > server-start -- if you create a tty emacsclient (with emacsclient -t) > in another tty, then step 3 will result in somefilename being opened > in an existing tty frame (as desired). Hmm... looks like I misunderstood the original bug. Are you saying that if you start tty1> emacs -f emacs-server tty2> emacsclient foo.bar that the emacsclient causes a new frame to be opened in tty2 or in tty1 (it should be in tty1)? Stefan