From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/52164 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.gnus.general Subject: Re: Ideas for .no Gnus Date: Fri, 02 May 2003 21:50:24 -0400 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: ding-owner@lists.math.uh.edu Message-ID: <4nhe8cssrj.fsf@lockgroove.bwh.harvard.edu> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1051926572 19405 80.91.224.249 (3 May 2003 01:49:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sat, 3 May 2003 01:49:32 +0000 (UTC) Cc: ding@gnus.org Original-X-From: ding-owner+M707@lists.math.uh.edu Sat May 03 03:49:30 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19Bm9a-00052h-00 for ; Sat, 03 May 2003 03:49:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19BmAe-0004FC-00; Fri, 02 May 2003 20:50:36 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19BmAW-0004F6-00 for ding@lists.math.uh.edu; Fri, 02 May 2003 20:50:28 -0500 Original-Received: (qmail 64405 invoked by alias); 3 May 2003 01:50:28 -0000 Original-Received: (qmail 64399 invoked from network); 3 May 2003 01:50:28 -0000 Original-Received: from clifford.bwh.harvard.edu (134.174.9.41) by sclp3.sclp.com with SMTP; 3 May 2003 01:50:28 -0000 Original-Received: from lockgroove.bwh.harvard.edu (lockgroove [134.174.9.133]) by clifford.bwh.harvard.edu (8.10.2+Sun/8.11.0) with ESMTP id h431oPI18791; Fri, 2 May 2003 21:50:25 -0400 (EDT) Original-Received: (from tzz@localhost) by lockgroove.bwh.harvard.edu (8.11.6+Sun/8.11.0) id h431oPf25429; Fri, 2 May 2003 21:50:25 -0400 (EDT) Original-To: replies@frank-schmitt.net 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" Mail-Followup-To: replies@Frank-Schmitt.net, ding@gnus.org In-Reply-To: (Frank Schmitt's message of "Fri, 02 May 2003 23:22:11 +0200") User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (usg-unix-v) Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:52164 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:52164 On Fri, 02 May 2003, usereplyto@Frank-Schmitt.net wrote: > *themes*: It would be quite cool if people could export their > settings for the various ...-line-format variables (especially > gnus-summary-line-format) to a file so they can easily exchange > them, Gnus could also include some predefined sets (e.g. classic, > slrn-like, table-format...) Are all those variables called *-format? Is there a canonical list in Gnus somewhere? > *configuration wizard*: This one is AFAIK already quite high in the > todo list of Larsi, my idea would be short questions in the > minibuffer and an explanation of what the user is supposed to > answer in the active buffer, but there are probably other, better > ways of implementing it. I would love to see this. Configuring the spam.el features is very hard for a beginner, so I'll definitely contribute to the wizards' code and testing when their design solidifies. I think the design and configuration format were discussed on the ding list not too long ago. > *images in summary buffer* It would be nice, if it was possible to > use small images instead of characters for the different marks in > summary buffer. I like this idea! > *cache of seen message-ids* Discussed some threads above: Some > solution which helps synchronizing .newsrc between two Gnus which > read news from different servers would help all those who read > e.g. at home from a Leafnode and at work from some other news > server. gnus-registry.el keeps track of all seen message IDs automatically for you, both by tracking message move/delete/copy/spool actions, and by registering messages whenever it enters a group. It does this by keeping a hashtable for fast access, converted to an alist when it's saved to the .newsrc.eld as gnus-registry-alist. Currently only the group name(s) for the article is kept, but there is room for arbitrary extra data *associated with the message ID*. Unfortunately the alist grows quickly, so maybe I will move gnus-registry-alist to a file separate from .newsrc.eld. I just finished the gnus-registry.el basic work, and now I'm about to start using it for tracking message processing with spam.el. There's no problem with hooking into the registry for tracking other message data, but check with me since I want to keep the API consistent. Thanks Ted