emacs-devel
[Top][All Lists]
Advanced

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

Re: emacsclient's option decoding code


From: Juri Linkov
Subject: Re: emacsclient's option decoding code
Date: Thu, 13 Nov 2008 22:03:04 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (x86_64-pc-linux-gnu)

>   . 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)

-- 
Juri Linkov
http://www.jurta.org/emacs/




reply via email to

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