Re: Change in emacsclient behavior

[Edward O'Connor <hober0@gmail.com>]

Richard Stallman <rms@gnu.org> 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.
> So I think it should depend on the value of `pop-up-frames'.

> Are there any arguments against testing `pop-up-frames'?

To me, the main usefulness of multi-tty functionality is for when I'm
remotely logging in to a machine on which I already have a long-running
Emacs. For instance, on workstation A I have an Emacs running with X11
frames. I SSH into A from some other machine B, and would like to open a
TTY frame within that SSH session.

I think this, or situations similar to it, is the scenario envisioned by
the change in emacsclient -- note the NEWS entry specifically calls out
the support for "opening a new *terminal* frame."

So, yes, I don't normally make new frames, but `pop-up-frames' strikes
me as precisely the wrong variable to test in this scenario. Also,
popping up the existing X11 frame does no good in this case.