From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87527 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: [RFC] Gnus generalized search, part II Date: Fri, 28 Apr 2017 21:16:18 -0700 Message-ID: <87pofvhmr1.fsf@ericabrahamsen.net> References: <87zif930mt.fsf@ericabrahamsen.net> <87shkx5z17.fsf@ericabrahamsen.net> <87zif3fupv.fsf@hanan> <87h91b3z2m.fsf@ericabrahamsen.net> <87tw5aztpy.fsf@ericabrahamsen.net> <87wpa6iif7.fsf@hanan> <87o9vh90cy.fsf@ericabrahamsen.net> <87r30dz618.fsf@hanan> <87y3uk2xxz.fsf@ericabrahamsen.net> <87tw58f6no.fsf@hanan> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1493439401 25366 195.159.176.226 (29 Apr 2017 04:16:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sat, 29 Apr 2017 04:16:41 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+m35742@lists.math.uh.edu Sat Apr 29 06:16:35 2017 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from mxfilter-048035.atla03.us.yomura.com ([107.189.48.35]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1d4Jo9-0006SJ-Q6 for ding-account@gmane.org; Sat, 29 Apr 2017 06:16:33 +0200 X-Yomura-MXScrub: 1.0 Original-Received: from lists1.math.uh.edu (unknown [129.7.128.208]) by mxfilter-048035.atla03.us.yomura.com (Halon) with ESMTPS id a3405e17-2c92-11e7-b087-b499baabecb2; Sat, 29 Apr 2017 04:16:37 +0000 (UTC) Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.87) (envelope-from ) id 1d4Jo7-0006hF-JD; Fri, 28 Apr 2017 23:16:31 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1d4Jo5-0006ga-D2 for ding@lists.math.uh.edu; Fri, 28 Apr 2017 23:16:29 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1d4Jo4-0000dR-BX for ding@lists.math.uh.edu; Fri, 28 Apr 2017 23:16:29 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1d4Jo2-0000y5-VI for ding@gnus.org; Sat, 29 Apr 2017 06:16:27 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1d4Jnv-0006Ek-Sf for ding@gnus.org; Sat, 29 Apr 2017 06:16:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 45 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:ypuBGyJoQDL8OtW14SK0ZS6wfHQ= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87527 Archived-At: Andrew Cohen writes: >>>>>> "Eric" == Eric Abrahamsen writes: > > > [...] > > > Eric> BTW, I patched Gnorb to use the nnselect backend instead of > Eric> its own awful jury-rigged nngnorb backend. So far all is > Eric> working great, both with ephemeral and persistent groups. Very > Eric> nice to have a simpler solution to that! > > Great! Did you try anything other than imap? Only imap so far. Gnorb uses the registry to get group+msg-id pairs, then calls gnus-request-head to get the article number, then makes the vectors out of that. Theoretically it shouldn't matter what the backend is, but... At some point I'll bit the bullet and set up a proper Gnus testing environment. > A (small) word of warning---I encountered a bug (not, in fact, a bug in > any of the new stuff, but rather something so ancient I can't even find > anything about the relevant code in the git logs:)) that can corrupt the > info-list for groups. It gets triggered only in a very rare > circumstance: if you are replying to a message from a summary buffer in > which the message resides in a group other than the summary buffer group > (this basically never happens unless you are using nnselect or nnir, in > which case it happens frequently) AND the setting up of the message > buffer and/or the sending of the message FAIL, then the > gnus-newsgroup-name gets the wrong value and this causes various info > structures to get set improperly. It won't delete any mail but it can > get the marks rather confused. > > I have a fix that I will push shortly. In the meantime to avoid > complications: if you try to reply to a message and it fails for any > reason, leave the summary buffer with "Q" rather than "q" so it doesn't > try to update info. Ugh, that sounds very much like Gnus. I've never hit that one in particular, but I'm glad you're fixing it. There's still something terribly fragile about marks; I wonder if more uses of gnus-atomic-* or at least just unwind-protect wouldn't be helpful.