From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: Change in emacsclient behavior
Date: Fri, 31 Aug 2007 10:06:18 +0200 [thread overview]
Message-ID: <87veaw5ds5.fsf@baldur.tsdh.de> (raw)
In-Reply-To: <jwvveawmcqb.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 31 Aug 2007 02:39:08 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> I think this change is a mistake:
>> +** Emacsclient has been extended to support opening a new terminal
>> +frame. Its behavior has been changed to open a new Emacs frame by
>> +default. Use the -c option to get the old behavior of opening files in
>> +the currently selected Emacs frame.
>
>> For people that normally don't make new frames, this will be a
>> hassle.
>
> Agreed. It may also be a hassle for people who use multiple frames
> because IIUC it will create only one frame per emacsclient rather than
> one per file, like I use.
>
>> So I think it should depend on the value of `pop-up-frames'.
>
> I disagree. It should just revert to the old behavior (i.e. revert
> the "-c" arg to emacsclient).
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.
But then -c --current-frame would't make sense. How about -m
--make-frame?
BTW: The man page needs to be updated, too.
Bye,
Tassilo
--
Chuck Norris has never won an Academy Award for acting... because he's
not acting.
next prev parent reply other threads:[~2007-08-31 8:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 20:50 Change in emacsclient behavior Richard Stallman
2007-08-30 21:04 ` Drew Adams
2007-08-31 18:21 ` Richard Stallman
2007-08-31 18:26 ` Drew Adams
2007-08-30 21:23 ` Eli Zaretskii
2007-08-30 21:41 ` Henrik Enberg
2007-08-31 18:21 ` Richard Stallman
2007-09-01 7:41 ` Eli Zaretskii
2007-09-01 8:26 ` David Kastrup
2007-08-31 6:39 ` Stefan Monnier
2007-08-31 8:06 ` Tassilo Horn [this message]
2007-08-31 14:31 ` Stefan Monnier
2007-09-02 18:52 ` Juri Linkov
2007-09-02 19:20 ` David Kastrup
2007-09-02 20:14 ` Juri Linkov
2007-09-02 20:34 ` David Kastrup
2007-09-02 20:44 ` Tom Tromey
2007-09-03 18:26 ` Richard Stallman
2007-09-02 23:20 ` Manoj Srivastava
2007-09-02 19:34 ` Tassilo Horn
2007-09-02 20:14 ` Juri Linkov
2007-09-03 19:15 ` Tassilo Horn
2007-09-03 15:31 ` Jeremy Maitin-Shepard
2007-09-03 18:26 ` Richard Stallman
2007-09-03 20:37 ` Stefan Monnier
2007-09-03 23:46 ` Juri Linkov
2007-09-04 23:08 ` Davis Herring
2007-09-05 20:02 ` Richard Stallman
2007-09-05 20:34 ` David Kastrup
2007-09-07 6:30 ` Richard Stallman
2007-09-07 7:06 ` David Kastrup
2007-09-08 7:01 ` Richard Stallman
2007-08-31 8:09 ` David Kastrup
2007-08-31 14:29 ` Stefan Monnier
2007-09-03 5:47 ` Edward O'Connor
2007-09-04 0:56 ` Richard Stallman
2007-09-04 5:56 ` David Kastrup
2007-09-04 22:57 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87veaw5ds5.fsf@baldur.tsdh.de \
--to=tassilo@member.fsf.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).