From: "Károly Lo\"rentey" <karoly@lorentey.hu>
To: emacs-devel@gnu.org
Subject: Re: multi-tty branch created
Date: Fri, 18 May 2007 20:02:16 +0200 [thread overview]
Message-ID: <f2kpni$ulj$1@sea.gmane.org> (raw)
In-Reply-To: <jwv8xbnghrp.fsf-monnier+emacs@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1373 bytes --]
Stefan Monnier wrote:
>> $ 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 ;-)
I hope so as well, but there is always room for tweaking the defaults if
I happened to choose something wrong.
I find that the current default settings fit me like a glove, but that's
no big wonder. :-) I'm very interested in what others think about the
behaviour of emacsclient, and if there is anything that doesn't work for
them as well as it could.
> 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.
Emacsclient can now consistently open a frame even if X is not
available, so I would argue existing users will find the new default
easier to use as well. If they do object, but only then, should we
consider reverting the default to the old behaviour. I personally find
the new emacsclient is really rather more pleasant to use than the old
one.
I wouldn't like to hide the new feature set because we're afraid
somebody somewhere might find it offensive, but if people did object,
then I'd easily accept such a decision.
--
Karoly
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
[-- Attachment #2: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2007-05-18 18:02 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
2007-05-18 18:02 ` Károly Lo"rentey [this message]
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='f2kpni$ulj$1@sea.gmane.org' \
--to=karoly@lorentey.hu \
--cc=emacs-devel@gnu.org \
/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.