From: Colin Baxter <m43cap@yandex.com>
To: info-gnus-english@gnu.org
Subject: Re: No gnus connection with emacs-27 SOLVED
Date: Fri, 17 Apr 2020 12:41:00 +0100 [thread overview]
Message-ID: <87y2qu731v.fsf@yandex.com> (raw)
In-Reply-To: <87blnqu1qm.fsf@yandex.com>
>>>>> "Colin" == Colin Baxter <m43cap@yandex.com> writes:
Colin> Hello, I can connect to my news groups using emacs-26.3, no
Colin> problem, but not with emacs-27 (or emacs-28). Has something
Colin> changed?
Colin> The relevant (I think!) portion of my ~/.gnus.el is
Colin> (setq gnus-select-method '(nntp "news.gmane.io"))
Colin> Emacs-26.3 accepts this, but emacs-27 gives the error:
Colin> Opening nntp server on news...failed: >>> (error news/nntp No
Colin> address associated with hostname)
I was launching emacs-27 via the "-q" option and then loading settings
via an elisp config file (don't ask me why!). It seems that emacs-27 had
no way of knowing it had to use ~/.gnus.el when receiving a M-x gnus <RET>
instruction. The solution is therefore to either
M-x load-library <RET> ~/.gnus.el <RET>
prior to launching gnus, or to put
(load-library "~/.gnus.el")
in the original elisp config file.
I hadn't realised before that the "-q" switch is such a killer!
Best wishes,
Colin Baxter
URL: http://www.Colin-Baxter.com
---------------------------------------------------------------------
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
---------------------------------------------------------------------
The sole cause of all human misery is the inability of people to sit
quietly in their rooms. Blaise Pascal, 1670
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2020-04-17 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 5:20 No gnus connection with emacs-27 Colin Baxter
2020-04-17 11:41 ` Colin Baxter [this message]
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=87y2qu731v.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).