[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacsclient bug

From: Sascha Wilde
Subject: Re: emacsclient bug
Date: Thu, 07 Feb 2008 10:03:51 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

Richard Stallman <address@hidden> wrote:

>       > Of course, if your Emacs server has both X11 and tty frames, then "-c"
>       > will arbitrarily open either a tty frame or an X11 frame depending on
>       > which frame happens to be selected when the emacsclient connects to 
> it.
>     Given that, taking into account the current frame when emacsclient
>     connects does not seem like a good idea.
> I disagree.  I think that what -c does is the right default.
> It says "make a new frame".  Making it on the same terminal
> is clearly the best default.
> You can specify additional options to say where the new frame should go.

No objections here, but I thought that `-c' would explicitly state "open a
new X11 frame (if available)" in contrast to `-t' which is documented as
"Open a new Emacs frame on the current terminal".

If this isn't supposed to be the case, an option saying: open a new X11
Frame on the current $DISPLAY is needed.  Currently only the combination
of `-c' and `-d' opens an new X11 frame, and `-d' requires an explicitly
given display (which is annoying for the reasons stated in my original

Sascha Wilde : "GUIs normally make it simple to accomplish simple 
             : actions and impossible to accomplish complex actions."
             : (Doug Gwyn - 22/Jun/91 in comp.unix.wizards)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]