From: Richard Copley <rcopley@gmail.com>
To: Noam Postavsky <npostavs@users.sourceforge.net>,
GNU bug tracker automated control server
<control@debbugs.gnu.org>
Cc: 27658@debbugs.gnu.org
Subject: bug#27658: 26.0.50; response parsing hangs when using tls.el and gnutls-cli.exe on Windows
Date: Wed, 12 Jul 2017 11:10:17 +0100 [thread overview]
Message-ID: <CAPM58ojp_Eyj58-g2YiJ0LwCzEv0_ntoWQSp3oo=Ve_4ROKprg@mail.gmail.com> (raw)
In-Reply-To: <87bmoqfqz8.fsf@users.sourceforge.net>
tags 27658 wontfix
close 27658
thank you
On 12 July 2017 at 01:17, <npostavs@users.sourceforge.net> wrote:
> Richard Copley <rcopley@gmail.com> writes:
>
>> Ensure Emacs is using "gnutls-cli.exe" instead of "libgnutls-30.dll"
>> by (a) removing the DLL from your path or (b) configuring Emacs with
>> the "--without-gnutls" configure option.
>
> In https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23759#8 Eli said:
>
> TLS connections on MS-Windows are supported via the GnuTLS library.
> External TLS programs will never work correctly on Windows, since
> they use signals to communicate with Emacs. So there's little sense
> in fixing this issue, because the result will not work anyway.
>
I see, thank you.
That's a lot of hours I'll never get back. No big deal! But a little comment
near the top of "tls.el", or somewhere, to let people know not to bother,
would be nice.
next prev parent reply other threads:[~2017-07-12 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 22:18 bug#27658: 26.0.50; response parsing hangs when using tls.el and gnutls-cli.exe on Windows Richard Copley
2017-07-12 0:17 ` npostavs
2017-07-12 10:10 ` Richard Copley [this message]
2017-07-12 12:09 ` npostavs
2017-07-13 2:42 ` Richard Copley
2017-07-13 15:48 ` Eli Zaretskii
2017-07-13 17:06 ` Richard Copley
2017-07-14 9:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ojp_Eyj58-g2YiJ0LwCzEv0_ntoWQSp3oo=Ve_4ROKprg@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=27658@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.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 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.