From: Eli Zaretskii <eliz@gnu.org>
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: cyd@stupidchicken.com, pandyacus@sbcglobal.net, emacs-devel@gnu.org
Subject: Re: (featurep 'multi-tty) => t on Windows
Date: Fri, 12 Dec 2008 18:27:45 -0500 [thread overview]
Message-ID: <E1LBHQ9-0002DL-5W@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0812120823k434d82f9n1aaead806d03b177@mail.gmail.com> (lekktu@gmail.com)
> Date: Fri, 12 Dec 2008 17:23:13 +0100
> From: "Juanma Barranquero" <lekktu@gmail.com>
> Cc: pandyacus@sbcglobal.net, cyd@stupidchicken.com, emacs-devel@gnu.org
>
> > Since emacsclient
> > cannot test Emacs features
>
> Not sure I understand what you mean:
>
> C:\> emacsclient --eval "(featurep 'multi-tty)"
> t
That's Emacs who evaluated the expression, not emacsclient, and doing
something with that in normal emacsclient usage is impossible. What I
meant is that you users cannot tweak emacsclient to do something like
"if this Emacs supports feature XYZ use option -N, otherwise use
option -M" (although one could write a shell script to do that).
emacsclient doesn't have an extension language that could make use of
that paradigm.
> > If I _am_ right, we should simply stop providing `multi-tty', while it
> > is still not too late.
>
> Perhaps; I'm not opposed to removing it. But I think that, if some
> package author finds a use for it in the future, it will be cleaner to
> check (featurep 'multi-tty) than (f?boundp whatever).
Only if we don't already have other features that could be checked
instead.
And btw, I don't think Emacs practice agrees with you in general: we
have quite a few features that cannot be tested with featurep, because
no code `provide'd them. Just grep the Lisp sources for fboundp.
next prev parent reply other threads:[~2008-12-12 23:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 12:54 (featurep 'multi-tty) => t on Windows Juanma Barranquero
2008-12-03 13:29 ` dhruva
2008-12-10 10:47 ` Juanma Barranquero
2008-12-10 14:00 ` Chong Yidong
2008-12-10 14:05 ` Juanma Barranquero
2008-12-10 16:16 ` Chong Yidong
2008-12-11 9:47 ` Juanma Barranquero
2008-12-11 17:35 ` Chetan Pandya
2008-12-11 23:24 ` Eli Zaretskii
2008-12-11 23:39 ` Juanma Barranquero
2008-12-12 12:01 ` Eli Zaretskii
2008-12-12 12:14 ` Juanma Barranquero
2008-12-12 12:54 ` Eli Zaretskii
2008-12-12 16:23 ` Juanma Barranquero
2008-12-12 23:27 ` Eli Zaretskii [this message]
2008-12-12 23:50 ` Juanma Barranquero
2008-12-13 2:43 ` Eli Zaretskii
2008-12-13 6:03 ` mail
2008-12-13 10:24 ` Eli Zaretskii
2008-12-13 11:01 ` Juanma Barranquero
2008-12-13 16:13 ` Stefan Monnier
2008-12-13 16:59 ` Juanma Barranquero
2008-12-14 2:42 ` Stefan Monnier
2008-12-14 3:11 ` Juanma Barranquero
2008-12-13 11:40 ` Richard M Stallman
2008-12-13 16:58 ` Juanma Barranquero
2008-12-12 4:38 ` Chetan Pandya
2008-12-12 12:03 ` Eli Zaretskii
2008-12-11 23:17 ` Eli Zaretskii
2008-12-11 23:35 ` Juanma Barranquero
2008-12-12 11:52 ` Eli Zaretskii
2008-12-12 12:08 ` Juanma Barranquero
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=E1LBHQ9-0002DL-5W@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=pandyacus@sbcglobal.net \
/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).