Re: emacsclient's option decoding code

[mail@justinbogner.com]

Juri Linkov <juri@jurta.org> writes:

>>   . if -c was specified, try creating a GUI frame, and failing that,
>>     try a tty frame;
>>
>>   . if --tty was specified, try make-frame-on-tty, if it fails, try
>>     using the current tty or a GUI frame.
>
> This looks mostly clear for me.  The only thing I don't understand is why
> we need -c?  Emacs has no option for creating a GUI frame and has -nw for
> running on a tty, so why should emacsclient be different?  The following
> rules are more consistent with the traditional Emacs invocation:
>
>   . if -nw was specified, try make-frame-on-tty, if it fails, try
>     using the current tty or a GUI frame;
>
>   . if no option specified, try creating a GUI frame, and failing that,
>     try a tty frame.
>
> for consistency with
>
>   emacsclient            = emacs          (create a new GUI frame)
>   emacsclient -nw        = emacs -nw      (run emacs on a tty)
>   emacsclient FILE       = emacs FILE     (open a file in a new GUI frame)
>   emacsclient -nw FILE   = emacs -nw FILE (open a file in a tty)

But emacsclient has to additionally support "use the existing frame",
which is what it does (and has always done) when no arguments are
specified.

-- 
No group of professionals meets except to conspire against the public at large.
		-- Mark Twain