From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Server name included in name of groups from gnus-select-method
Date: Mon, 05 May 2003 17:04:17 +0200 [thread overview]
Message-ID: <ilu3cjtqvta.fsf@latte.josefsson.org> (raw)
In-Reply-To: <u1xzdet5w.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Mon, 05 May 2003 09:42:19 +0200")
Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
> I'm absolutely sure. I hit F to find new groups on my local news server
> and got the message "one group arrived", then I tried to U name.of.group
> but Gnus told me "no match". Then I entered server buffer, hit <ret> with
> point over the server (my only nntp server, no ssh connection) and all
> old groups were shown with the correct names, only the new one had the
> nntp+127.0.0.1: prefix.
There was a change to gnus-group-prefixed-name recently, maybe you can
try to revert that patch, or try the patch below.
Index: gnus.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus.el,v
retrieving revision 6.181
diff -u -p -u -w -r6.181 gnus.el
--- gnus.el 3 May 2003 16:47:18 -0000 6.181
+++ gnus.el 5 May 2003 15:04:48 -0000
@@ -3188,6 +3188,7 @@ server is native)."
(setq method (gnus-server-to-method method)))
(if (or (not method)
(and (not full) (gnus-server-equal method "native"))
+ (and (not full) (gnus-server-equal method gnus-select-method))
;;;!!! This might not be right. We'll see...
;(string-match ":" group)
)
next prev parent reply other threads:[~2003-05-05 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 21:29 Frank Schmitt
2003-05-04 21:59 ` Johan Bockgård
2003-05-04 21:59 ` Johan Bockgård
2003-05-04 22:10 ` Johan Bockgård
2003-05-04 22:46 ` Johan Bockgård
2003-05-04 23:22 ` Simon Josefsson
2003-05-04 23:47 ` Harry Putnam
2003-05-05 7:42 ` Frank Schmitt
2003-05-05 15:04 ` Simon Josefsson [this message]
2003-05-05 15:15 ` Frank Schmitt
2003-05-05 20:29 ` Frank Schmitt
2003-05-05 17:50 ` Frank Haun
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=ilu3cjtqvta.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@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.
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).