From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Any way to control which articles Gnus summary shows by default? Date: Wed, 04 Apr 2018 15:30:19 +0800 Message-ID: <87sh8bsa2c.fsf@ericabrahamsen.net> References: <86lge3ric2.fsf@zoho.com> <87vad78nh2.fsf@web.de> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1522827105 13809 195.159.176.226 (4 Apr 2018 07:31:45 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 4 Apr 2018 07:31:45 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Wed Apr 04 09:31:40 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f3ctQ-0003Ui-M2 for geh-help-gnu-emacs@m.gmane.org; Wed, 04 Apr 2018 09:31:40 +0200 Original-Received: from localhost ([::1]:40102 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f3cvV-0006LG-ST for geh-help-gnu-emacs@m.gmane.org; Wed, 04 Apr 2018 03:33:49 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39209) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f3cuu-0006ID-9j for help-gnu-emacs@gnu.org; Wed, 04 Apr 2018 03:33:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f3cun-0006tS-Ka for help-gnu-emacs@gnu.org; Wed, 04 Apr 2018 03:33:12 -0400 Original-Received: from [195.159.176.226] (port=49527 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f3cun-0006qN-Ci for help-gnu-emacs@gnu.org; Wed, 04 Apr 2018 03:33:05 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1f3csf-0002Zh-Da for help-gnu-emacs@gnu.org; Wed, 04 Apr 2018 09:30:53 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 53 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:8dBqsXKtI1XN4Em1F7L919763hU= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.159.176.226 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:116335 Archived-At: Michael Heerdegen writes: > Emanuel Berg writes: > >> Interesting but, isn't this exactly what happens when you tick an >> article? So is there some side-effect that is undesired for this >> purpose or why don't you want to use it? > > I still try to find a good workflow for my Inbox. In the past, I used > to tick nearly all articles, or make them unread, just to make them > appear the next time I select the group. > > What I want in general is more control: I want to decide myself how Gnus > decides which articles it presents to me when I select a group. In > particular, I want to have it depend on the information present in the > registry. > > >> What do you mean by "set" article? > > I wrote "set unread" or so and meant "make the article unread". > > >> BTW `M M i' is undefined for me so maybe it is a new feature in Emacs >> 25 or did you configure that? > > It's a feature when you enable the Gnus registry: > > (info "(gnus) Store custom flags and keywords") > > Seems not many people use it so far, though. > > >> If you indeed got it to work, how about adding it to some hook/advice >> each time you enter a group? > > I think you shouldn't need a hack to do this kind of thing. A hack > would probably call `gnus-summary-limit', but it would be better if it > would be configurable out of the box. Which I think is not the case. > The code responsible for group selection is quite complex, but I have > the impression that these things are hardcoded. I agree that the process should be made more flexible, and would be happy to help work on a better solution that we can add to Gnus. That would happen at my typical pace of code contribution, though, which is best measured in months :) Some might think Gnus is over-customizable, but some aspects of customization, like posting styles, is both flexible and usable. It would be nice to provide similar access for group article selection, which is another core aspect of Gnus usage behavior. E