From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: lekktu@gmail.com, cyd@stupidchicken.com, emacs-devel@gnu.org
Subject: Re: emacsclient's option decoding code
Date: Thu, 13 Nov 2008 06:10:49 +0200 [thread overview]
Message-ID: <u8wrop8om.fsf@gnu.org> (raw)
In-Reply-To: <jwvy6zou0tr.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: lekktu@gmail.com, cyd@stupidchicken.com, emacs-devel@gnu.org
> Date: Wed, 12 Nov 2008 15:56:25 -0500
>
> > But this is guesswork at best, and cannot possibly DTRT in every
> > possible use-case, because emacsclient have no way of knowing what the
> > Emacs server can or cannot do.
>
> Some of the decisions could benefit from being moved to/from the client
> from/to the server, indeed.
> But returning an error if the user requests something that can't be done
> is often better than trying to be clever.
I don't see why erroring out is better.
> > . if --display=DISPLAY was specified, try the given DISPLAY, if that
> > fails, try ":0.0", if that fails, try using a tty;
>
> :0.0 may be miles away from the user's eyes, so if $DISPLAY fails,
> better signal an error and let the user manually switch to :0.0 if
> that's what he wants to do.
If :0.0 is miles away, there's no difference between an error and
display miles away: in both cases, the user needs to fix something and
reinvoke. What I suggest is better because if :0.0 is NOT miles away,
it does TRT, while erroring does not.
> It might be OK to provide an option to do that, but silently doing so
> without the user's constent may be worse than signalling an error and
> letting *her* switch to the appropriate tty.
We do it today already, with the kind of guesswork we have in
emacsclient.
next prev parent reply other threads:[~2008-11-13 4:10 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 14:04 emacsclient's option decoding code Eli Zaretskii
2008-11-02 2:13 ` Stefan Monnier
2008-11-02 21:45 ` Chong Yidong
2008-11-02 22:00 ` Juanma Barranquero
2008-11-02 23:18 ` Chong Yidong
2008-11-03 0:50 ` Juanma Barranquero
2008-11-03 4:14 ` Eli Zaretskii
2008-11-03 12:12 ` Juanma Barranquero
2008-11-03 20:06 ` Eli Zaretskii
2008-11-03 20:19 ` Chong Yidong
2008-11-04 4:20 ` Eli Zaretskii
2008-11-04 16:40 ` Chong Yidong
2008-11-06 11:56 ` Juanma Barranquero
2008-11-03 21:26 ` Juanma Barranquero
2008-11-04 4:19 ` Eli Zaretskii
2008-11-06 12:08 ` Juanma Barranquero
2008-11-07 9:53 ` Eli Zaretskii
2008-11-07 11:42 ` Juanma Barranquero
2008-11-07 11:47 ` Juanma Barranquero
2008-11-07 14:36 ` Eli Zaretskii
2008-11-07 14:42 ` Juanma Barranquero
2008-11-10 18:22 ` Juanma Barranquero
2008-11-10 18:36 ` Chong Yidong
2008-11-10 23:33 ` Juanma Barranquero
2008-11-11 4:09 ` Eli Zaretskii
2008-11-11 4:14 ` Chong Yidong
2008-11-11 21:16 ` Eli Zaretskii
2008-11-11 9:39 ` Juanma Barranquero
2008-11-11 15:37 ` Juanma Barranquero
2008-11-11 21:24 ` Eli Zaretskii
2008-11-11 23:36 ` Juanma Barranquero
2008-11-12 4:22 ` Eli Zaretskii
2008-11-12 9:41 ` Juanma Barranquero
2008-11-12 19:14 ` Eli Zaretskii
2008-11-12 21:05 ` Juanma Barranquero
2008-11-13 4:12 ` Eli Zaretskii
2008-11-13 8:34 ` Juanma Barranquero
2008-11-12 19:37 ` Eli Zaretskii
2008-11-12 2:31 ` Stefan Monnier
2008-11-12 9:33 ` Juanma Barranquero
2008-11-12 15:56 ` Stefan Monnier
2008-11-12 16:37 ` Juanma Barranquero
2008-11-12 17:13 ` Stefan Monnier
2008-11-13 1:16 ` Lennart Borgman
2008-11-13 4:18 ` Eli Zaretskii
2008-11-13 9:00 ` Juanma Barranquero
2008-11-13 15:45 ` Dan Nicolaescu
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:05 ` Juanma Barranquero
2008-11-13 16:08 ` Dan Nicolaescu
2008-11-12 19:36 ` Eli Zaretskii
2008-11-12 20:56 ` Stefan Monnier
2008-11-13 4:10 ` Eli Zaretskii [this message]
2008-11-13 4:29 ` mail
2008-11-13 20:54 ` Eli Zaretskii
2008-11-13 21:27 ` mail
2008-11-13 22:30 ` Eli Zaretskii
2008-11-13 23:54 ` mail
2008-11-13 20:03 ` Juri Linkov
2008-11-13 20:40 ` mail
2008-11-13 21:08 ` Thorsten Bonow
2008-11-13 22:01 ` Thorsten Bonow
2008-11-15 2:58 ` Evil Boris
2008-11-07 14:35 ` Eli Zaretskii
2008-11-03 14:45 ` Juanma Barranquero
2008-11-03 19:59 ` Eli Zaretskii
2008-11-03 20:03 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u8wrop8om.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).