all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Fri, 12 Dec 2014 21:04:22 +0200	[thread overview]
Message-ID: <83zjasr8p5.fsf@gnu.org> (raw)
In-Reply-To: <jwvy4qcsu90.fsf-monnier+emacsbugs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: hi@yagnesh.org,  19346@debbugs.gnu.org,  larsi@gnus.org
> Date: Fri, 12 Dec 2014 11:39:29 -0500
> 
> I have no idea what you're talking about, really.

Then I'm surprised you are arguing.

> If the library needs to advertise more precisely the exact set of
> features it happens to provide, then this will probably have to be
> done in an ad-hoc manner (tho maybe the `subfeature' arg of
> `featurep' could be used for this: it's the kind of thing it was
> meant for, although in practice it seems it's never used).

Yes, libraries will need to advertise more than one feature.  And no,
doing that ad-hoc is not the best solution.  Nothing prevents us from
designing a better one, since we don't yet have any history to be
compatible to.  I don't see why we would need to give up and stop
short of designing a more flexible solution before the ad-hockery
dictates its solution.





  reply	other threads:[~2014-12-12 19:04 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 [this message]
2014-12-12 21:56                           ` Stefan Monnier
2014-12-13  7:43                             ` Eli Zaretskii
2014-12-13 14:21                               ` Stefan Monnier
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zjasr8p5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=19346@debbugs.gnu.org \
    --cc=hi@yagnesh.org \
    --cc=larsi@gnus.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.