From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: hi@yagnesh.org, 19346@debbugs.gnu.org, larsi@gnus.org
Subject: bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p
Date: Sat, 13 Dec 2014 09:21:28 -0500 [thread overview]
Message-ID: <jwvtx0zpr7l.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83ppboq9jq.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 13 Dec 2014 09:43:37 +0200")
> How harder would it be if 'foo-available-p', or 'require', or 'load',
> or whatever we call it, would return a list of the features supported
> by the module?
It'll be `require' because that's what it already is.
We can't really change what `require' returns.
And even if we could, it would suffer from the usual problem that we
don't know which subfeatures will be important to know.
Hence fboundp,
Stefan
next prev parent reply other threads:[~2014-12-13 14:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:57 bug#19346: 25.0.50; url-http-parse-headers: Symbol's function definition is void: gnutls-available-p Yagnesh Raghava Yakkala
2014-12-11 15:57 ` Lars Magne Ingebrigtsen
2014-12-11 16:08 ` Ted Zlatanov
2014-12-11 16:16 ` Lars Magne Ingebrigtsen
2014-12-11 18:00 ` Eli Zaretskii
2014-12-11 19:16 ` Stefan Monnier
2014-12-11 19:48 ` Ted Zlatanov
2014-12-11 21:03 ` Eli Zaretskii
2014-12-11 22:58 ` Ted Zlatanov
2014-12-12 0:02 ` Stefan Monnier
2014-12-12 0:21 ` Ted Zlatanov
2014-12-12 1:33 ` Stefan Monnier
2014-12-12 7:58 ` Eli Zaretskii
2014-12-12 14:40 ` Stefan Monnier
2014-12-12 14:54 ` Eli Zaretskii
2014-12-12 16:39 ` Stefan Monnier
2014-12-12 19:04 ` Eli Zaretskii
2014-12-12 21:56 ` Stefan Monnier
2014-12-13 7:43 ` Eli Zaretskii
2014-12-13 14:21 ` Stefan Monnier [this message]
2014-12-13 15:20 ` Eli Zaretskii
2014-12-12 13:19 ` Ted Zlatanov
2014-12-12 14:47 ` Stefan Monnier
2014-12-12 7:49 ` Eli Zaretskii
2014-12-12 14:42 ` Stefan Monnier
2014-12-12 14:55 ` Eli Zaretskii
2014-12-12 16:33 ` Stefan Monnier
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=jwvtx0zpr7l.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=19346@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hi@yagnesh.org \
--cc=larsi@gnus.org \
/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).