From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: csant Newsgroups: gmane.emacs.devel Subject: [multi-tty] X or tty (was Re: Emacs port status) Date: Fri, 18 May 2007 21:56:53 +0200 Organization: csant.info Message-ID: References: <464CC097.10700@gnu.org> <85abw3up91.fsf@lola.goethe.zz> <464DF9D8.7080001@lorentey.hu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1179518226 26332 80.91.229.12 (18 May 2007 19:57:06 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 18 May 2007 19:57:06 +0000 (UTC) Cc: emacs-devel To: =?utf-8?B?S8Ohcm9seSBMxZFyZW50ZXk=?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 18 21:57:05 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 1Hp8ZV-0000k0-17 for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 21:57:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hp8ZU-0001Hd-IO for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 15:57:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hp8ZR-0001HK-2w for emacs-devel@gnu.org; Fri, 18 May 2007 15:57:01 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hp8ZP-0001GT-2q for emacs-devel@gnu.org; Fri, 18 May 2007 15:56:59 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hp8ZO-0001GI-Tg for emacs-devel@gnu.org; Fri, 18 May 2007 15:56:58 -0400 Original-Received: from csant.info ([69.36.171.12]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hp8ZO-00031P-CT for emacs-devel@gnu.org; Fri, 18 May 2007 15:56:58 -0400 Original-Received: from fiore.malebolge (csant.info [69.36.171.12]) (authenticated bits=0) by csant.info (8.12.11.20060308/8.12.11) with ESMTP id l4IJusAs009150; Fri, 18 May 2007 13:56:56 -0600 User-Agent: Opera Mail/9.21 (Linux) X-MIME-Autoconverted: from 8bit to quoted-printable by csant.info id l4IJusAs009150 X-detected-kernel: Linux 2.4-2.6 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:71337 Archived-At: Some feedback as a *user* of this feature. Please disregard if I am =20 talking rubbish. On Fri, 18 May 2007 21:09:12 +0200, K=C3=A1roly L=C5=91rentey =20 wrote: > 1. Emacsclient opens a new frame by default. It prefers X, but > falls back to tty when necessary or when forced, just like Emacs > itself. The simplest case is running server and client both in X, and expected =20 behaviour would be for the client to prefer X. Equally obvious would be = =20 the case where no X is available, and both the server and the client run = =20 in console. I can easily see use cases for running the emacs server =20 without X (in screen, or in console) and expect emacsclients to draw thei= r =20 frame on the X display they are invoked on. I can a bit less easily =20 imagine cases where you'd run the server in X, and clients on a display =20 but wanting them to open the frame in terminal. In my personal workflow = I =20 am running both the server and the clients on an X display *in terminal* = =20 (-nw and -t respectively). It gets tedious to add a -t to each =20 emacsclient call, and I'd wish for it to be `smarter' in understanding =20 `what I mean'. Ideally, I'd like the client to inherit by default any `forced' flags set= =20 to the server, i.e. to start by default with -t when the server was =20 deliberately started -nw in an environment that does have $DISPLAY set. = =20 This could be overwritten in the client with -d . Would that break more expected behaviours than fix some? /c