Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: registry doc patch
Date: Fri, 19 Sep 2008 08:19:17 +0900	[thread overview]
Message-ID: <b4mtzcdujnu.fsf@jpl.org> (raw)
In-Reply-To: <86iqswnr9w.fsf@lifelogs.com>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

>>>>> 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/


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 3662 bytes --]

--- 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
 

  reply	other threads:[~2008-09-18 23:19 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87abfkmuko.fsf@jondo.cante.net>
2008-08-13  8:29 ` Group, Summary buffers: End of line contain whitespaces Katsumi Yamaoka
2008-08-13 18:56   ` Reiner Steib
2008-08-13 21:47     ` Jari Aalto
2008-08-15 16:31       ` jidanni
2008-08-19 11:48       ` Miles Bader
2008-08-22 15:52   ` Ted Zlatanov
2008-08-27 23:01     ` Miles Bader
2008-08-28 13:51       ` Ted Zlatanov
2008-08-29 11:15         ` Reiner Steib
2008-08-29 15:12           ` bugs and features (was: Group, Summary buffers: End of line contain whitespaces) Ted Zlatanov
2008-09-15 21:00             ` registry doc patch (was: bugs and features) Ted Zlatanov
2008-09-16  9:17               ` registry doc patch Rupert Swarbrick
2008-09-16 13:36                 ` Ted Zlatanov
2008-09-16 12:30               ` Magnus Henoch
2008-09-16 13:39                 ` Ted Zlatanov
2008-09-18 23:19                   ` Katsumi Yamaoka [this message]
2008-09-19 16:19                     ` Ted Zlatanov
2008-09-23 19:18                       ` Reiner Steib
2008-09-24  0:37                         ` Katsumi Yamaoka
2008-09-24  6:45                           ` Katsumi Yamaoka
2008-09-24 16:45                             ` Reiner Steib
2008-09-24 16:44                           ` informat.el: `Info-split' split size (was: registry doc patch) Reiner Steib
2008-09-24 23:58                             ` informat.el: `Info-split' split size Katsumi Yamaoka
2008-09-25  3:10                               ` Eli Zaretskii
2008-09-25  4:01                                 ` Katsumi Yamaoka
2008-09-25 23:10                               ` Katsumi Yamaoka
2008-08-29 13:51         ` Group, Summary buffers: End of line contain whitespaces Ted Zlatanov
2008-08-29 15:31         ` Daiki Ueno
2008-08-29 15:55           ` Ted Zlatanov
2008-08-30  5:07             ` Katsumi Yamaoka
2008-08-30  9:33               ` Ted Zlatanov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b4mtzcdujnu.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).