From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/87579 Path: news.gmane.org!.POSTED!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: bug#21071: Gnus message flags must be set before expiration, not afterwards Date: Thu, 26 Jan 2017 20:43:53 +0100 Message-ID: <87sho5obd2.fsf@gnus.org> References: <87mvyx2c20.fsf@vostro.rath.org> <87fv4p2b9n.fsf@vostro.rath.org> <87bncbu2un.fsf@vostro.rath.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1496101966 27139 195.159.176.226 (29 May 2017 23:52:46 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 29 May 2017 23:52:46 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux) Cc: ding , Nikolaus Rath To: 21071@debbugs.gnu.org Original-X-From: ding-owner+M35578@lists.math.uh.edu Thu Jan 26 20:45:48 2017 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cWpyy-0007t2-RC for ding-account@gmane.org; Thu, 26 Jan 2017 20:45:20 +0100 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 1cWpyy-0005m6-AX; Thu, 26 Jan 2017 13:45:20 -0600 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by lists1.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1cWpyx-0005lU-1I for ding@lists.math.uh.edu; Thu, 26 Jan 2017 13:45:19 -0600 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.87) (envelope-from ) id 1cWpyv-0001Ka-VD for ding@lists.math.uh.edu; Thu, 26 Jan 2017 13:45:18 -0600 Original-Received: from hermes.netfonds.no ([80.91.224.195]) by quimby.gnus.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1cWpyu-0001R9-I8 for ding@gnus.org; Thu, 26 Jan 2017 20:45:16 +0100 Original-Received: from 2.150.50.220.tmi.telenormobil.no ([2.150.50.220] helo=mouse) by hermes.netfonds.no with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cWpys-000470-Fa; Thu, 26 Jan 2017 20:45:16 +0100 In-Reply-To: <87bncbu2un.fsf@vostro.rath.org> (Nikolaus Rath's message of "Tue, 06 Oct 2015 14:03:12 -0700") List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:87579 Nikolaus Rath writes: > I did not find any specific guarantees on when > gnus-summary-prepare-exit-hook is called in the documentation, but that > doesn't mean that people are not relying on the current calling > order. Would a change like that nevertheless be acceptable? > > Alternatively, is what do people think about removing > gnus-summary-expire-articles from the default value of > gnus-summary-prepare-exit-hook and explicitly calling > gnus-summary-expire-articles from gnus-summary-exit? I don't know why that function is in that hook by default; it seems kinda messy. But removing things from hooks isn't that easy since people add things, or set values explicitly. But we could call gnus-summary-expire-articles in the natural place unless it's in that hook, perhaps? And then remove it from the default value and hope for the best. Patches welcome. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no