Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@pdc.kth.se>
Cc: ding@gnus.org
Subject: Re: Bug in 5.8.5 (copying articles)
Date: 21 Apr 2000 23:34:49 +0200	[thread overview]
Message-ID: <iluk8hrdtom.fsf@badis.pdc.kth.se> (raw)
In-Reply-To: Arcady Genkin's message of "21 Apr 2000 16:20:57 -0400"

Arcady Genkin <a.genkin@utoronto.ca> writes:

> I think I discovered another bug in the latest CVS gnus. I tried to
> copy an article from an nntp group into an nnimap one, or from an
> nnimap into nnimap. I use "B c" from summary buffer. Here's the trace:
> 
> Signaling: (wrong-type-argument listp "archive")
>   car("archive")

This patch might solve that problem, could you see if it does?

This is the same patch as Chris Brierley re-sent earlier, only without
byte-compile warnings.

2000-03-01  Simon Josefsson  <jas@pdc.kth.se>

	* gnus-sum.el (gnus-read-move-group-name): 
	(gnus-summary-move-article): Use `gnus-group-method' to find out
	what method the manually entered group belong to.
	`gnus-group-name-to-method' doesn't return any method parameters
	and `gnus-find-method-for-group' uses `gnus-group-name-to-method'
	for new groups so they wouldn't work.

Index: gnus-sum.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/gnus-sum.el,v
retrieving revision 5.104
diff -w -u -u -w -r5.104 gnus-sum.el
--- gnus-sum.el	2000/04/21 20:18:21	5.104
+++ gnus-sum.el	2000/04/21 21:27:23
@@ -7333,7 +7333,8 @@
 	     articles prefix))
       (set (intern (format "gnus-current-%s-group" action)) to-newsgroup))
     (setq to-method (or select-method
-			(gnus-group-method to-newsgroup)))
+			(gnus-server-to-method
+			 (gnus-group-method to-newsgroup))))
     ;; Check the method we are to move this article to...
     (unless (gnus-check-backend-function
 	     'request-accept-article (car to-method))
@@ -9030,7 +9031,8 @@
 				  (mapcar (lambda (el) (list el))
 					  (nreverse split-name))
 				  nil nil nil
-				  'gnus-group-history)))))
+				  'gnus-group-history))))
+         (to-method (gnus-server-to-method (gnus-group-method to-newsgroup))))
     (when to-newsgroup
       (if (or (string= to-newsgroup "")
 	      (string= to-newsgroup prefix))
@@ -9038,15 +9040,12 @@
       (unless to-newsgroup
 	(error "No group name entered"))
       (or (gnus-active to-newsgroup)
-	  (gnus-activate-group to-newsgroup nil nil
-			       (gnus-group-method to-newsgroup))
+	  (gnus-activate-group to-newsgroup nil nil to-method)
 	  (if (gnus-y-or-n-p (format "No such group: %s.  Create it? "
 				     to-newsgroup))
-	      (or (and (gnus-request-create-group
-			to-newsgroup (gnus-group-method to-newsgroup))
+	      (or (and (gnus-request-create-group to-newsgroup to-method)
 		       (gnus-activate-group
-			to-newsgroup nil nil
-			(gnus-group-method to-newsgroup))
+			to-newsgroup nil nil to-method)
 		       (gnus-subscribe-group to-newsgroup))
 		  (error "Couldn't create group %s" to-newsgroup)))
 	  (error "No such group: %s" to-newsgroup)))



  reply	other threads:[~2000-04-21 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-21 20:20 Arcady Genkin
2000-04-21 21:34 ` Simon Josefsson [this message]
2000-04-21 21:50   ` Arcady Genkin
2000-04-21 22:00     ` Simon Josefsson

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=iluk8hrdtom.fsf@badis.pdc.kth.se \
    --to=jas@pdc.kth.se \
    --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).