From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Change in emacsclient behavior Date: Sun, 02 Sep 2007 21:52:21 +0300 Organization: JURTA Message-ID: <87veatxcrz.fsf@jurta.org> References: <87veaw5ds5.fsf@baldur.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1188759734 24567 80.91.229.12 (2 Sep 2007 19:02:14 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 2 Sep 2007 19:02:14 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Sep 02 21:02:12 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 1IRuhw-0000Tt-Ob for ged-emacs-devel@m.gmane.org; Sun, 02 Sep 2007 21:02:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRuhv-0000pQ-Cn for ged-emacs-devel@m.gmane.org; Sun, 02 Sep 2007 15:02:03 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IRuhr-0000nC-Kv for emacs-devel@gnu.org; Sun, 02 Sep 2007 15:01:59 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IRuhr-0000mA-2l for emacs-devel@gnu.org; Sun, 02 Sep 2007 15:01:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IRuhq-0000m3-Pu for emacs-devel@gnu.org; Sun, 02 Sep 2007 15:01:58 -0400 Original-Received: from relay02.kiev.sovam.com ([62.64.120.197]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IRuhq-0006Dp-2p for emacs-devel@gnu.org; Sun, 02 Sep 2007 15:01:58 -0400 Original-Received: from [83.170.232.243] (helo=smtp.svitonline.com) by relay02.kiev.sovam.com with esmtp (Exim 4.67) (envelope-from ) id 1IRuhT-0003u0-9C for emacs-devel@gnu.org; Sun, 02 Sep 2007 22:01:43 +0300 In-Reply-To: <87veaw5ds5.fsf@baldur.tsdh.de> (Tassilo Horn's message of "Fri\, 31 Aug 2007 10\:06\:18 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/23.0.50 (gnu/linux) X-Scanner-Signature: 1118cf21f7425d415ed61e91afc5cb63 X-DrWeb-checked: yes X-SpamTest-Envelope-From: juri@jurta.org X-SpamTest-Group-ID: 00000000 X-SpamTest-Header: Not Detected X-SpamTest-Info: Profiles 1426 [August 31 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {HEADERS: header Content-Type found without required header Content-Transfer-Encoding} X-SpamTest-Method: none X-SpamTest-Rate: 10 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release X-Detected-Kernel: FreeBSD 4.8-5.1 (or MacOS X 10.2-10.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:77609 Archived-At: > Normally I don't use several frames, but for emacsclients I like the new > behavior. Making it depend on pop-up-frames wouldn't help me, so I'm > for the reversed behavior of the -c option, too. How about the following default behavior of emacsclient: 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). 2. When invoked with -e or --eval, display the current frame and eval the expression on this frame. 3. When invoked with one FILE argument, create a new frame with the file buffer. 4. When invoked with multiple FILE arguments, create either one frame with windows containing all specified files' buffers, 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). The reason that is usually it's undesirable to change the window configuration of the current frame when visiting new files. However, evaluation of the expression can change it as well, e.g. emacsclient -e '(info)'. So the argument -c is still needed to force either creating a new frame or using the current one. Of course, when parsing is done on the Emacs side, this gives the user more power to decide what exactly to do. > But then -c --current-frame would't make sense. One possible mnemonic for -c is --create-frame. BTW, does anyone know how to start a detached Emacs server so that after logout and login I could connect to it with emacsclient? I tried nohup emacs -nw -f server-start but it writes to nohup.out emacs: standard input is not a tty and exits. Then I tried with the -batch argument, but this doesn't work neither. -- Juri Linkov http://www.jurta.org/emacs/