From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 11091@debbugs.gnu.org
Subject: bug#11091: 24.0.94; emacsclient -t
Date: Mon, 26 Mar 2012 16:03:09 +0200 [thread overview]
Message-ID: <CAAeL0SQ7Zu1HLa0jaGb66WsBFNCtNZz_Jb37kTJkMxfUmUhCBg@mail.gmail.com> (raw)
In-Reply-To: <jwvd37zfsgq.fsf-monnier+emacs@gnu.org>
On Mon, Mar 26, 2012 at 14:39, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> While we could put it in the manual, I think it'll be more useful to
> users if we can emit a warning when emacsclient requests something we
> can't do (e.g. open a tty frame when we're running in the Windows GUI).
The reason we unified -t and -c in the Windows' emacsclient is because
the user can then invoke emacslient -(c|t) from a shortcut or .CMD
file and not have to worry about the Emacs server instance being GUI
or console. The user already has an Emacs server running (or the call
to emacsclient will fail for other reasons, unrelated to c/t).
Emitting a warning in these cases seems to me more noisy than helpful.
Juanma
next prev parent reply other threads:[~2012-03-26 14:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 22:10 bug#11091: 24.0.94; emacsclient -t Dani Moncayo
2012-03-25 22:29 ` Dani Moncayo
2012-03-25 23:39 ` Juanma Barranquero
2012-03-25 23:45 ` Juanma Barranquero
2012-03-26 6:40 ` Dani Moncayo
2012-03-26 9:19 ` Juanma Barranquero
2012-03-26 9:25 ` Dani Moncayo
2012-03-26 9:27 ` Juanma Barranquero
2012-03-26 22:49 ` Dani Moncayo
2012-03-31 9:54 ` Eli Zaretskii
2012-03-31 11:38 ` Dani Moncayo
2012-03-31 11:45 ` Dani Moncayo
2012-04-11 16:40 ` Glenn Morris
2012-04-11 19:53 ` Dani Moncayo
2012-03-31 12:34 ` Eli Zaretskii
2012-04-01 8:44 ` Dani Moncayo
2012-04-01 17:13 ` Eli Zaretskii
2012-04-01 19:17 ` Dani Moncayo
2012-04-01 20:49 ` Eli Zaretskii
2012-04-02 7:01 ` Dani Moncayo
2012-04-02 17:36 ` Eli Zaretskii
2012-03-26 12:39 ` Stefan Monnier
2012-03-26 14:03 ` Juanma Barranquero [this message]
2012-03-26 19:15 ` Eli Zaretskii
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=CAAeL0SQ7Zu1HLa0jaGb66WsBFNCtNZz_Jb37kTJkMxfUmUhCBg@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=11091@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.