From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: Change in emacsclient behavior Date: Mon, 03 Sep 2007 14:26:06 -0400 Message-ID: References: <87veaw5ds5.fsf@baldur.tsdh.de> <87veatxcrz.fsf@jurta.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1188844299 27853 80.91.229.12 (3 Sep 2007 18:31:39 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 3 Sep 2007 18:31:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 03 20:31:38 2007 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 1ISGhz-0006e1-On for ged-emacs-devel@m.gmane.org; Mon, 03 Sep 2007 20:31:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ISGhy-0004RJ-DI for ged-emacs-devel@m.gmane.org; Mon, 03 Sep 2007 14:31:34 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ISGcv-0008Ai-QM for emacs-devel@gnu.org; Mon, 03 Sep 2007 14:26:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ISGcu-000888-Uo for emacs-devel@gnu.org; Mon, 03 Sep 2007 14:26:21 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ISGcu-00087p-KG for emacs-devel@gnu.org; Mon, 03 Sep 2007 14:26:20 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ISGcu-0000Am-Dm for emacs-devel@gnu.org; Mon, 03 Sep 2007 14:26:20 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1ISGcg-00067S-3x; Mon, 03 Sep 2007 14:26:06 -0400 In-reply-to: <87veatxcrz.fsf@jurta.org> (message from Juri Linkov on Sun, 02 Sep 2007 21:52:21 +0300) X-Detected-Kernel: Linux 2.6, seldom 2.4 (older, 4) 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:77671 Archived-At: 1. When invoked without arguments, display the current frame (-c uses the current frame, but this could be customizable to display the initial frame or any of existing frames). Ok. 2. When invoked with -e or --eval, display the current frame and eval the expression on this frame. Ok. 3. When invoked with one FILE argument, create a new frame with the file buffer. No. emacsclient should, by default, display files the same way C-x C-f does. server.el should simply call find-file. We already have lots of ways to customize C-x C-f, and we can add more if users want them. If server.el simply calls find-file, all these customization mechanisms will be available for it. 4. When invoked with multiple FILE arguments, create either one frame with windows containing all specified files' buffers, No, for the same reason. or if `pop-up-frames' is non-nil, create as many frames as there are file arguments (starting a new Emacs session already does this). That seems plausible for the case where `pop-up-frames' is non-nil.