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: multi-tty branch created Date: Thu, 17 May 2007 19:24:37 -0400 Message-ID: References: <87sla0rgs4.fsf@catnip.gol.com> <85abw8pyk7.fsf@lola.goethe.zz> <85646wpuqn.fsf@lola.goethe.zz> <464C7D1F.7000201@lorentey.hu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1179444287 20883 80.91.229.12 (17 May 2007 23:24:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 17 May 2007 23:24:47 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?iso-8859-1?Q?K=E1roly_Lorentey?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri May 18 01:24:46 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 1HopKv-0002OO-44 for ged-emacs-devel@m.gmane.org; Fri, 18 May 2007 01:24:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HopT3-0003Nv-RH for ged-emacs-devel@m.gmane.org; Thu, 17 May 2007 19:33:09 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HopT0-0003N6-Do for emacs-devel@gnu.org; Thu, 17 May 2007 19:33:06 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HopSz-0003Mu-Tm for emacs-devel@gnu.org; Thu, 17 May 2007 19:33:06 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HopSz-0003Mr-Ne for emacs-devel@gnu.org; Thu, 17 May 2007 19:33:05 -0400 Original-Received: from 18.red-83-50-230.dynamicip.rima-tde.net ([83.50.230.18] helo=alfajor.home) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HopKp-0006QY-NC for emacs-devel@gnu.org; Thu, 17 May 2007 19:24:40 -0400 Original-Received: by alfajor.home (Postfix, from userid 20848) id 8CBD21C5F9; Thu, 17 May 2007 19:24:37 -0400 (EDT) In-Reply-To: <464C7D1F.7000201@lorentey.hu> (=?iso-8859-1?Q?=22K=E1roly?= Lo"'s message of "Thu\, 17 May 2007 18\:04\:47 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.95 (gnu/linux) X-detected-kernel: 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:71290 Archived-At: >> For the sake of transparent backward compatibility, I'd make --current-frame >> the default, and use -nw as an argument to force the use of the new >> multi-tty feature. This way you only get the new feature when you ask >> for it. I normally prefer using an X11 frame over a tty frame, so I'd only >> want to use -nw in those cases where it matters (typically when the >> bandwidth is limited). > You assume that emacsclient now opens a tty frame even if X is > available. That's not the case. Emacsclient works like Emacs: it > prefers X, and falls back to the tty only if X is unavailable or the > user forces opening a tty frame by supplying "-t" (the emacsclient > equivalent to "-nw"). > $ emacsclient > ==> X frame There are *many* different ways to create new frames (one per "session", one per file, reuse old ones or not, ...). I hope you got it right ;-) > $ emacsclient -t > ==> tty frame > $ emacsclient -c > ==> no new frame Maybe it's OK. Note that when I added the --display argument, I was careful to not automatically use the $DISPLAY envvar, in order to preserve backward compatibility, so users have to say --display "$DISPLAY" if they want it. My experience with Emacs is that when introducing a new feature, any minor backward incompatibility will slow down adoption, so it's easier to just let new features disabled by default. See the comment-style variable for another example ;-) > I agree that "-t" should be renamed "-nw"; in fact this idea is even in > the README file. However, multi-character short options are a pain to > implement. I'd prefer if someone with more getopt experience would do > it instead. :-) I see. Yes, it's a problem with the current argument scheme, indeed. Stefan