Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: registry doc patch
Date: Fri, 19 Sep 2008 11:19:54 -0500	[thread overview]
Message-ID: <86bpykjefp.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mtzcdujnu.fsf@jpl.org>

On Fri, 19 Sep 2008 08:19:17 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote: 

>>>>>> Ted Zlatanov wrote:
>> Please let me know if you have corrections or it needs more detail
>> anywhere.

KY> Thank you for uploading the Gnus Registry manual.  It will be
KY> very useful for those who want to start using the registry (I'm
KY> not an exception ;-).  When having been translating the manual
KY> into Japanese[1], I found some oddities there.

KY> The menu entry had better be put in the `Top' node, too.

I thought I did that, oops.

KY> Conventionally `t' and `nil' are quoted with @code{} at least in
KY> the Gnus manual (even though they aren't so in a doc string).

KY> Some Lisp symbols used in values of the gnus-registry- variables
KY> aren't quoted.  Or they are quoted as if they are in Lisp forms.

KY> A patch is attached below.

Thanks for catching all those issues.  I applied your patch in your
name to expedite things.

Ted




  reply	other threads:[~2008-09-19 16: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
2008-09-19 16:19                     ` Ted Zlatanov [this message]
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=86bpykjefp.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).