From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/69098 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: editing nnimap articles Date: Fri, 09 Oct 2009 09:39:49 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <874oq8vdfu.fsf@lifelogs.com> References: <87ocohn1tt.fsf@uwo.ca> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1255099319 5454 80.91.229.12 (9 Oct 2009 14:41:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 9 Oct 2009 14:41:59 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M17514@lists.math.uh.edu Fri Oct 09 16:41:49 2009 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1MwGf4-0000AP-0Z for ding-account@gmane.org; Fri, 09 Oct 2009 16:41:38 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1MwGdr-0008F9-Pp; Fri, 09 Oct 2009 09:40:23 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1MwGdp-0008Er-P2 for ding@lists.math.uh.edu; Fri, 09 Oct 2009 09:40:21 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1MwGdo-00051M-Bh for ding@lists.math.uh.edu; Fri, 09 Oct 2009 09:40:21 -0500 Original-Received: from lo.gmane.org ([80.91.229.12]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1MwGdn-0006JW-00 for ; Fri, 09 Oct 2009 16:40:19 +0200 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1MwGdm-0007oH-IC for ding@gnus.org; Fri, 09 Oct 2009 16:40:18 +0200 Original-Received: from 38.98.147.130 ([38.98.147.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Oct 2009 16:40:18 +0200 Original-Received: from tzz by 38.98.147.130 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 09 Oct 2009 16:40:18 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 38.98.147.130 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6;d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:nWXEorr9K4LhFrlwDySz2Kl1Hhk= X-Spam-Score: -0.7 (/) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:69098 Archived-At: On Thu, 08 Oct 2009 15:05:34 -0400 Dan Christensen wrote: DC> I receive so many attachments that I find it necessary to use DC> gnus-mime-save-part-and-strip to delete them from my archived messages. DC> I'm in the process of converting from nnfolder to nnimap, and so I'd DC> like to investigate how hard it would be to extend nnimap to allow DC> article editing. DC> My sense is that it should not be hard, since it just requires the DC> creation of a new article and the deletion of the old one, and both of DC> those are operations that nnimap can perform. (In fact, I just noticed DC> that `B I' is able to create a new empty article in an nnimap group.) DC> In digging through the code, it looks to me like what would be needed DC> would be an implementation of nnimap-request-replace-article. DC> Would that just be a matter of combining nnimap-request-accept-article DC> with something like DC> (imap-message-flags-add (format "%d" article) DC> "\\Seen \\Deleted") DC> ? DC> Would this work? Can someone help me fill in the details? With IMAP, you have to expunge as well, but then you may expunge other deleted articles at the wrong time. So you may just have to live with the old \\Deleted article until the next time the user or Gnus expunges the group, and it will still show up in the summary buffer. I think that's acceptable. It would be good if this edit told the registry about the changeover by getting the record for the old message ID and storing it with the new one. I can add that hook. Otherwise this looks good to me, I'm all for it. I've been doing it the roundabout way (move to nnmaildir, edit, move back) for years. Ted