unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: andrewjmoreton@gmail.com
Cc: 20159@debbugs.gnu.org
Subject: bug#20159: 24.4; url-retrieve invokes same callback twice with kill-buffer
Date: Fri, 27 Mar 2015 22:40:19 +0300	[thread overview]
Message-ID: <83iodm1b6k.fsf@gnu.org> (raw)
In-Reply-To: <83lhii1c08.fsf@gnu.org>

> Date: Fri, 27 Mar 2015 22:22:31 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 20159@debbugs.gnu.org
> 
> > From: Andy Moreton <andrewjmoreton@gmail.com>
> > Date: Fri, 27 Mar 2015 16:59:39 +0000
> > 
> > > No one volunteered, so I did it myself, see commit d133cf8 on master.
> > 
> > This change broke gnus for me on a mingw64 x64 build of emacs, as gnutls
> > seems unable to connect to the NNTP server at gmane.org.
> 
> Sorry about that.  Does Gnus do something windows-specific for
> connecting?  Perhaps that specific treatment relied on something that
> is no longer true on Windows.

Another, perhaps more probable culprit is the emacs_gnutls_pull
function.  It calls sys_read, where I made some changes to support the
non-blocking connect.  Perhaps emacs_gnutls_pull cannot cope with some
results of those changes, and itself needs to be amended.





  reply	other threads:[~2015-03-27 19:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 20:46 bug#20159: 24.4; url-retrieve invokes same callback twice with kill-buffer Christopher Wellons
2015-03-21 21:00 ` Eli Zaretskii
2015-03-21 21:48   ` Christopher Wellons
2015-03-22 17:31     ` Eli Zaretskii
2015-03-27  9:52       ` Eli Zaretskii
2015-03-27 16:59         ` Andy Moreton
2015-03-27 19:22           ` Eli Zaretskii
2015-03-27 19:40             ` Eli Zaretskii [this message]
2015-03-28  7:39               ` Eli Zaretskii
2015-03-28 10:56                 ` Andy Moreton
2015-03-28 11:28                   ` Eli Zaretskii
2015-12-25 18:30 ` Lars Ingebrigtsen
2016-03-01  4:04   ` Lars Ingebrigtsen
2016-03-01  4:08   ` Lars Ingebrigtsen

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=83iodm1b6k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=20159@debbugs.gnu.org \
    --cc=andrewjmoreton@gmail.com \
    /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).