From: TSUCHIYA Masatoshi <tsuchiya@namazu.org>
Subject: Trouble in creating a group that has been seen ephemerally
Date: Thu, 09 Jun 2005 12:09:52 +0000 [thread overview]
Message-ID: <878y1ju3xr.fsf@tsuchiya.vaj.namazu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
Hi,
I encountered an error which occurs creating a group that had already
been seen ephemerally. Here is a procedure to reproduce the trouble
that I saw.
(1) Call `gnus-group-enter-server-mode' and enter *Server* buffer.
(2) Select a server, and open an unseen group ephemerally.
(3) Jump to *Group* buffer.
(4) Call `gnus-group-make-group' and specifies the group, the backend,
and the server which you saw in the 2nd step. You will recieve
the following error message.
Group backend+server:group already exists
In order to avoid this problem, I propose the attached patch.
But, I have noticed that this issue had already been discussed 5 years
ago and 2 years ago.
2000-07-13 Simon Josefsson <jas@pdc.kth.se>
* gnus-srvr.el (gnus-browse-read-group): Don't pass fully
qualified group names to `gnus-group-read-ephemeral-group'.
2003-04-13 Lars Magne Ingebrigtsen <larsi@gnus.org>
* gnus-srvr.el (gnus-browse-read-group): Don't give the real name
to the ephemeral entry, but the prefixed name.
Therefore, I worry that my proposal has ill effects. Which change is
right?
--
TSUCHIYA Masatoshi
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 443 bytes --]
--- gnus-srvr.el 30 May 2005 06:45:52 -0000 7.15
+++ gnus-srvr.el 9 Jun 2005 11:46:57 -0000
@@ -872,7 +872,8 @@
(if (or (not (gnus-get-info group))
(gnus-ephemeral-group-p group))
(unless (gnus-group-read-ephemeral-group
- group gnus-browse-current-method nil
+ (gnus-group-short-name group)
+ gnus-browse-current-method nil
(cons (current-buffer) 'browse)
nil nil nil number)
(error "Couldn't enter %s" group))
reply other threads:[~2005-06-09 12:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=878y1ju3xr.fsf@tsuchiya.vaj.namazu.org \
--to=tsuchiya@namazu.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).