From: Daiki Ueno <ueno@unixuser.org>
Subject: [PATCH] Can't connect to the new server in gnus-server-mode
Date: Fri, 12 Apr 2002 12:19:32 +0900 [thread overview]
Message-ID: <ff343918-c906-4721-91fc-360773536169@deisui.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Every time, from the *Server* buffer, I attempt to register the new
server with some attributes (such as nntp-address, nntp-port-number)
which are disregarded and opening the server tends to fail.
The reason for that seems that `gnus-server-method-cache' needs to be
updated when finished editing the server, since it takes precedence
over `gnus-server-alist' there.
Here is the patch to fix this.
2002-04-12 Daiki Ueno <ueno@unixuser.org>
* gnus-srvr.el (gnus-server-set-info): Clear
`gnus-server-method-cache' when `gnus-server-alist' is changed.
[-- Attachment #2: gnus-srvr.el.diff --]
[-- Type: application/octet-stream, Size: 854 bytes --]
Index: lisp/gnus-srvr.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-srvr.el,v
retrieving revision 6.23
diff -u -F^( -r6.23 gnus-srvr.el
--- lisp/gnus-srvr.el 2002/02/20 00:15:31 6.23
+++ lisp/gnus-srvr.el 2002/04/12 03:21:47
@@ -380,7 +380,11 @@ (defun gnus-server-set-info (server info
(concat "(gnus-server-set-info \"" server "\" '"
(prin1-to-string info) ")"))
(let* ((server (nth 1 info))
- (entry (assoc server gnus-server-alist)))
+ (entry (assoc server gnus-server-alist))
+ (cached (assoc server gnus-server-method-cache)))
+ (if cached
+ (setq gnus-server-method-cache
+ (delq cached gnus-server-method-cache)))
(if entry (setcdr entry info)
(setq gnus-server-alist
(nconc gnus-server-alist (list (cons server info))))))))
[-- Attachment #3: Type: text/plain, Size: 25 bytes --]
Regards,
--
Daiki Ueno
next reply other threads:[~2002-04-12 3:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 3:19 Daiki Ueno [this message]
2002-04-12 3:44 ` Katsumi Yamaoka
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=ff343918-c906-4721-91fc-360773536169@deisui.org \
--to=ueno@unixuser.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).