From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/83435 Path: news.gmane.org!not-for-mail From: Alberto Luaces Newsgroups: gmane.emacs.gnus.general Subject: Re: re-splitting old mail: nnimap version Date: Mon, 01 Jul 2013 12:26:51 +0200 Message-ID: <874nced190.fsf@eps142.cdf.udc.es> References: <87wqpd6wkh.fsf@ericabrahamsen.net> <87bo6menkk.fsf@eps142.cdf.udc.es> <87ehbid3r8.fsf@ericabrahamsen.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1372674509 26585 80.91.229.3 (1 Jul 2013 10:28:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Jul 2013 10:28:29 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M31695@lists.math.uh.edu Mon Jul 01 12:28:28 2013 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UtbLO-0007uZ-EY for ding-account@gmane.org; Mon, 01 Jul 2013 12:28:26 +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 1UtbK8-0001K3-DR; Mon, 01 Jul 2013 05:27:08 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1UtbK7-0001Ju-8G for ding@lists.math.uh.edu; Mon, 01 Jul 2013 05:27:07 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1UtbK5-0001Uy-RQ for ding@lists.math.uh.edu; Mon, 01 Jul 2013 05:27:07 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]) by quimby.gnus.org with esmtp (Exim 4.72) (envelope-from ) id 1UtbK4-0004MX-D9 for ding@gnus.org; Mon, 01 Jul 2013 12:27:04 +0200 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1UtbK3-0006mu-Ic for ding@gnus.org; Mon, 01 Jul 2013 12:27:03 +0200 Original-Received: from pcmecanismos.eps.cdf.udc.es ([193.144.52.105]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Jul 2013 12:27:03 +0200 Original-Received: from aluaces by pcmecanismos.eps.cdf.udc.es with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 01 Jul 2013 12:27:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 39 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pcmecanismos.eps.cdf.udc.es User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux) Cancel-Lock: sha1:cKd6RseUp/PI2QHr+hE4kaWjM90= X-Spam-Score: -1.9 (-) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:83435 Archived-At: Eric Abrahamsen writes: > Alberto Luaces writes: > >> Eric Abrahamsen writes: >> >>> With nnmail you could re-split existing messages by respooling them. The >>> respool process only triggers splitting for nnmail, however, not for >>> nnimap. Is there any other nnimap-specific trick? >> >> You can try to set the nnimap-split-predicate variable to UNDELETED just >> for one time in order to split all the messages, according to the >> documentation. > > Thanks! That variable doesn't exist here, though, with a gnus from git. > Is it maybe something that's built or checked dynamically? Oops... I'm using gnus from Emacs23, so yours is much more recent. I remember that there was some renaming with nnimap splitting variables in order to be identical to those of nnmail. Maybe you can search nnimap.el for "split-predicate" in order to see if it got renamed too. For reference, here is the old documentation for the variable: « nnimap-split-predicate is a variable defined in `nnimap.el'. Its value is "UNSEEN" This variable is potentially risky when used as a file local variable. Documentation: The predicate used to find articles to split. If you use another IMAP client to peek on articles but always would like nnimap to split them once it's started, you could change this to "UNDELETED". Other available predicates are available in RFC2060 section 6.4.4. » -- Alberto