From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/67404 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: registry doc patch Date: Fri, 19 Sep 2008 08:19:17 +0900 Organization: Emacsen advocacy group Message-ID: References: <87abfkmuko.fsf@jondo.cante.net> <86bpzlt5cq.fsf@lifelogs.com> <87prnut63f.fsf@catnip.gol.com> <86vdxlfdtn.fsf@lifelogs.com> <87zlmwoyvs.fsf@marauder.physik.uni-ulm.de> <86zlmvkg8p.fsf_-_@lifelogs.com> <86vdwxnmzf.fsf_-_@lifelogs.com> <8763ow9ssf.fsf@freemail.hu> <86iqswnr9w.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Trace: ger.gmane.org 1221780054 19697 80.91.229.12 (18 Sep 2008 23:20:54 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 18 Sep 2008 23:20:54 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M15855@lists.math.uh.edu Fri Sep 19 01:21:49 2008 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1KgSom-0000pU-7d for ding-account@gmane.org; Fri, 19 Sep 2008 01:21:48 +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 1KgSn4-0003Xv-Ml; Thu, 18 Sep 2008 18:20:02 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1KgSn2-0003Xc-Vc for ding@lists.math.uh.edu; Thu, 18 Sep 2008 18:20:00 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.69) (envelope-from ) id 1KgSmz-00071X-7x for ding@lists.math.uh.edu; Thu, 18 Sep 2008 18:20:00 -0500 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.36 #1 (Debian)) id 1KgSn2-00037i-00 for ; Fri, 19 Sep 2008 01:20:00 +0200 Original-Received: from localhost ([127.0.0.1]:46820) by orlando.hostforweb.net with esmtpa (Exim 4.69) (envelope-from ) id 1KgSmO-00005H-Nd for ding@gnus.org; Thu, 18 Sep 2008 18:19:21 -0500 X-Hashcash: 1:20:080918:ding@gnus.org::lorkNJ335kjwnJRU:00005XQj X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.60 (gnu/linux) Cancel-Lock: sha1:T0Nrs1YSG9y0nvrOdXXmNsBaFhM= X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.6 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:67404 Archived-At: --=-=-= >>>>> Ted Zlatanov wrote: > Please let me know if you have corrections or it needs more detail > anywhere. Thank you for uploading the Gnus Registry manual. It will be very useful for those who want to start using the registry (I'm not an exception ;-). When having been translating the manual into Japanese[1], I found some oddities there. The menu entry had better be put in the `Top' node, too. Conventionally `t' and `nil' are quoted with @code{} at least in the Gnus manual (even though they aren't so in a doc string). Some Lisp symbols used in values of the gnus-registry- variables aren't quoted. Or they are quoted as if they are in Lisp forms. A patch is attached below. Regards, [1] http://cvs.m17n.org/viewcvs/root/gnus-doc-ja/ --=-=-= Content-Type: text/x-patch Content-Disposition: inline --- gnus.texi~ 2008-09-16 21:41:21 +0000 +++ gnus.texi 2008-09-18 23:17:52 +0000 @@ -827,6 +827,7 @@ * Fuzzy Matching:: What's the big fuzz? * Thwarting Email Spam:: Simple ways to avoid unsolicited commercial email. * Spam Package:: A package for filtering and processing spam. +* The Gnus Registry:: A package for tracking messages by Message-ID. * Other modes:: Interaction with other modes. * Various Various:: Things that are really various. @@ -26606,13 +26607,13 @@ @defvar gnus-registry-use-long-group-names Whether the registry will use long group names. It's recommended to -set this to t, although everything works if you don't. Future +set this to @code{t}, although everything works if you don't. Future functionality will require it. @end defvar @defvar gnus-registry-max-entries -The number (an integer or nil for unlimited) of entries the registry -will keep. +The number (an integer or @code{nil} for unlimited) of entries the +registry will keep. @end defvar @defvar gnus-registry-cache-file @@ -26627,7 +26628,7 @@ Every message has a Message-ID, which is unique, and the registry remembers it. When the message is moved or copied, the registry will notice this and offer the new group as a choice to the splitting -strategy. +strategy. When a followup is made, usually it mentions the original message's Message-ID in the headers. The registry knows this and uses that @@ -26651,17 +26652,17 @@ @defvar gnus-registry-track-extra This is a list of symbols, so it's best to change it from the -Customize interface. By default it's nil, but you may want to track -subject and sender as well when splitting by parent. It may work -for you. It can be annoying if your mail flow is large and people -don't stick to the same groups. +Customize interface. By default it's @code{nil}, but you may want to +track @code{subject} and @code{sender} as well when splitting by parent. +It may work for you. It can be annoying if your mail flow is large and +people don't stick to the same groups. @end defvar @defvar gnus-registry-split-strategy This is a symbol, so it's best to change it from the Customize -interface. By default it's nil, but you may want to set it to -@code{'majority} or @code{'first} to split by sender or subject based -on the majority of matches or on the first found. +interface. By default it's @code{nil}, but you may want to set it to +@code{majority} or @code{first} to split by sender or subject based on +the majority of matches or on the first found. @end defvar @node Store custom flags and keywords @@ -26678,9 +26679,10 @@ it or evaluate the specific macros you'll need, but you probably don't want to bother). Use the Customize interface to modify the list. -By default this list has the Important, Work, Personal, To-Do, and -Later marks. They all have keyboard shortcuts like @kbd{M M i} for -Important, using the first letter. +By default this list has the @code{Important}, @code{Work}, +@code{Personal}, @code{To-Do}, and @code{Later} marks. They all have +keyboard shortcuts like @kbd{M M i} for Important, using the first +letter. @end defvar @defun gnus-registry-mark-article @@ -26712,7 +26714,7 @@ If any extra entries are precious, their presence will make the registry keep the whole entry forever, even if there are no groups for the Message-ID and if the size limit of the registry is reached. By -default this is just @code{'(marks)} so the custom registry marks are +default this is just @code{(marks)} so the custom registry marks are precious. @end defvar --=-=-=--