all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change in emacsclient behavior
Date: Sun, 02 Sep 2007 21:20:57 +0200	[thread overview]
Message-ID: <85myw4q3fq.fsf@lola.goethe.zz> (raw)
In-Reply-To: <87veatxcrz.fsf@jurta.org> (Juri Linkov's message of "Sun\, 02 Sep 2007 21\:52\:21 +0300")

Juri Linkov <juri@jurta.org> writes:

>> 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.
>
> How about the following default behavior of emacsclient:

I don't think that it makes sense to fantasize a whole bunch of
behaviors for emacsclient: emacsclient should be modeled to mimic
Emacs itself as closely as possible with regard to command line
options and stuff: that way, one does not need half a million of info
pages to explain how clever it is.

> 1. When invoked without arguments, display the current frame (-c
> uses the current frame, but this could be customizable to display
> the initial frame or any of existing frames).

Initial frame seems reasonable.

> 2. When invoked with -e or --eval, display the current frame and eval the
> expression on this frame.
>
> 3. When invoked with one FILE argument, create a new frame with the file
> buffer.
>
> 4. When invoked with multiple FILE arguments, create either one frame with
> windows containing all specified files' buffers, or if `pop-up-frames' is
> non-nil, create as many frames as there are file arguments (starting a new
> Emacs session already does this).

Too much cleverness.  Just do the same thing that is done on normal
Emacs startup.

> The reason that is usually it's undesirable to change the window
> configuration of the current frame when visiting new files.

That is no different from C-x C-f.

I can imagine one thing that could conceivably made to differentiate
between "C-x C-f"-like and "new Emacs session"-like behavior: if tty
and/or TERM indicate that emacsclient has been started from _within_
Emacs (for example, as an editor from a CVS command inside of an Emacs
shell or VC), then it does make more sense to treat this "C-x
C-f"-like than when emacsclient gets started from an independent
tty/terminal.


-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2007-09-02 19:20 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
2007-08-31 14:31     ` Stefan Monnier
2007-09-02 18:52     ` Juri Linkov
2007-09-02 19:20       ` David Kastrup [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85myw4q3fq.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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.