From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Károly Lorentey" <karoly@lorentey.hu>
Cc: emacs-devel@gnu.org
Subject: Re: multi-tty branch created
Date: Thu, 17 May 2007 19:24:37 -0400 [thread overview]
Message-ID: <jwv8xbnghrp.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <464C7D1F.7000201@lorentey.hu> ("Károly Lo"'s message of "Thu\, 17 May 2007 18\:04\:47 +0200")
>> 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
next prev parent reply other threads:[~2007-05-17 23:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-13 13:31 multi-tty branch created Miles Bader
2007-05-13 14:50 ` David Kastrup
2007-05-13 16:12 ` Miles Bader
2007-05-13 16:14 ` David Kastrup
2007-05-13 16:13 ` David Kastrup
2007-05-13 19:28 ` Robert J. Chassell
2007-05-16 13:24 ` Károly Lo"rentey
2007-05-16 13:46 ` Juanma Barranquero
2007-05-16 15:04 ` Károly Lőrentey
2007-05-16 15:34 ` David Kastrup
2007-05-16 16:11 ` Károly Lőrentey
2007-05-16 21:17 ` Jason Rumney
2007-05-16 16:20 ` Dan Nicolaescu
2007-05-16 17:39 ` David Kastrup
2007-05-16 20:48 ` Károly Lőrentey
2007-05-17 14:02 ` Stefan Monnier
2007-05-17 16:04 ` Károly Lo"rentey
2007-05-17 23:24 ` Stefan Monnier [this message]
2007-05-18 18:02 ` Károly Lo"rentey
2007-05-19 14:07 ` Stefan Monnier
2007-05-13 20:07 ` Jason Rumney
2007-05-14 10:21 ` Karoly Lorentey
2007-05-14 11:55 ` Jason Rumney
2007-05-15 13:03 ` Karoly Lorentey
2007-05-15 22:05 ` Ken Raeburn
2007-05-14 6:00 ` Manoj Srivastava
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv8xbnghrp.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=karoly@lorentey.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.