From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Using gnutls.c by default
Date: Mon, 02 May 2011 14:06:52 -0500 [thread overview]
Message-ID: <87sjswudkj.fsf@lifelogs.com> (raw)
In-Reply-To: m3k4e97z1s.fsf@quimbies.gnus.org
On Mon, 02 May 2011 20:11:27 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> Juanma has some W32 improvements in the queue. Also until the W32
>> builds have GnuTLS enabled I wouldn't make it the default.
LMI> Currently `open-network-stream' checks for `(fboundp
LMI> 'open-gnutls-stream)', which means that it won't use that unless you've
LMI> loaded gnutls.el. I was just thinking of checking for the C-level
LMI> `gnutls-book' instead, which would mean that it would be used by all
LMI> Emacsen that has gnutls.c compiled.
Juanma and I were just discussing having `gnutls-boot' throw an error if
the GnuTLS libraries can't be loaded. If you can catch those errors in
`open-network-stream' even when `gnutls-boot' is defined, I think that's
even better, as it will DTRT in all the cases.
Ted
next prev parent reply other threads:[~2011-05-02 19:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-02 13:54 Using gnutls.c by default Lars Magne Ingebrigtsen
2011-05-02 17:57 ` Ted Zlatanov
2011-05-02 18:11 ` Lars Magne Ingebrigtsen
2011-05-02 19:06 ` Ted Zlatanov [this message]
2011-05-02 22:50 ` Christoph Scholtes
2011-05-02 23:09 ` Juanma Barranquero
2011-05-05 10:42 ` Ted Zlatanov
2011-05-05 11:27 ` Juanma Barranquero
2011-05-05 11:50 ` Andy Moreton
2011-05-05 11:57 ` Juanma Barranquero
2011-05-05 14:00 ` Ted Zlatanov
2011-05-05 14:16 ` Robert Pluim
2011-05-05 14:36 ` Ted Zlatanov
2011-05-07 15:05 ` T.V. Raman
2011-05-08 0:03 ` Ted Zlatanov
2011-05-08 2:00 ` Stefan Monnier
2011-05-05 12:10 ` Christoph Scholtes
2011-05-05 12:15 ` Juanma Barranquero
2011-05-05 12:17 ` Christoph Scholtes
2011-05-05 13:22 ` Robert Pluim
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=87sjswudkj.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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).