unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Branham <alex.branham@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 37221@debbugs.gnu.org
Subject: bug#37221: 27.0.50; gnus fails to open connection post-NSM update
Date: Wed, 04 Sep 2019 10:04:11 -0500	[thread overview]
Message-ID: <87v9u8cdck.fsf@gmail.com> (raw)
In-Reply-To: <m2k1aop0u0.fsf@gmail.com> (Robert Pluim's message of "Wed, 04 Sep 2019 16:56:07 +0200")

On Wed 04 Sep 2019 at 16:56, Robert Pluim <rpluim@gmail.com> wrote:

> Iʼve spotted one possible problem: nsm-query runs even when the
> connection is unencrypted, which ends up doing (insert nil), which
> aborts the connection. Does the following help? (Lars, why is nsm
> prompting for unencrypted connections?)
>
> diff --git a/lisp/net/nsm.el b/lisp/net/nsm.el
> index 5e8381075b..7243ae8822 100644
> --- a/lisp/net/nsm.el
> +++ b/lisp/net/nsm.el
> @@ -788,7 +788,8 @@ nsm-check-plain-connection
>  (defun nsm-query (host port status what problems message)
>    ;; If there is no user to answer queries, then say `no' to everything.
>    (if (or noninteractive
> -	  nsm-noninteractive)
> +	  nsm-noninteractive
> +          (not status))
>        nil
>      (let ((response
>  	   (condition-case nil

nsm-query gets skipped now but the process is still killed (same
message, etc).

Thanks,
Alex





  parent reply	other threads:[~2019-09-04 15:04 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-29 16:56 bug#37221: 27.0.50; gnus fails to open connection post-NSM update Alex Branham
2019-09-02  9:33 ` Robert Pluim
2019-09-03 18:26   ` Alex Branham
2019-09-03 20:16     ` Robert Pluim
2019-09-04 13:13       ` Alex Branham
2019-09-04 13:37         ` Lars Ingebrigtsen
2019-09-04 14:00           ` Alex Branham
2019-09-04 14:16             ` Lars Ingebrigtsen
2019-09-04 14:24               ` Alex Branham
2019-09-04 14:35                 ` Lars Ingebrigtsen
2019-09-04 14:51                   ` Alex Branham
2019-09-04 14:56             ` Robert Pluim
2019-09-04 14:59               ` Lars Ingebrigtsen
2019-09-04 15:04                 ` Robert Pluim
2019-09-04 15:04               ` Alex Branham [this message]
2019-09-04 15:25                 ` Robert Pluim
2019-09-04 15:55                   ` Alex Branham
2019-09-04 17:00                     ` Robert Pluim
2019-09-04 17:06                       ` Lars Ingebrigtsen
2019-09-04 17:21                         ` Robert Pluim
2019-09-04 17:24                           ` Lars Ingebrigtsen
2019-09-04 19:30                             ` Robert Pluim
2019-09-04 19:37                               ` Lars Ingebrigtsen
2019-09-04 20:37                                 ` Robert Pluim
2019-09-04 20:41                                   ` Lars Ingebrigtsen
2019-09-04 21:49                                     ` 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=87v9u8cdck.fsf@gmail.com \
    --to=alex.branham@gmail.com \
    --cc=37221@debbugs.gnu.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).