From: yamaoka Date: Tue, 13 May 2003 08:16:29 +0000 (+0000) Subject: Synch to Gnus 200305130811. X-Git-Url: http://git.chise.org/gitweb/?a=commitdiff_plain;h=0ab511bafa2fffcf2277238736351151df755a8f;p=elisp%2Fgnus.git- Synch to Gnus 200305130811. --- diff --git a/texi/ChangeLog b/texi/ChangeLog index 3ac2e82..6b7f106 100644 --- a/texi/ChangeLog +++ b/texi/ChangeLog @@ -1,3 +1,8 @@ +2003-05-13 Simon Josefsson + + * gnus.texi (IMAP, Agent and IMAP, Oort Gnus): s/a/an/. Tiny + patch from Niklas Morberg . + 2003-05-12 Kevin Greiner * gnus.texi (Agent Visuals): Add. diff --git a/texi/gnus-ja.texi b/texi/gnus-ja.texi index 104d7a0..b39e0ad 100644 --- a/texi/gnus-ja.texi +++ b/texi/gnus-ja.texi @@ -24570,7 +24570,7 @@ the valid values. Gnus supports Cancel Locks in News. This means a header @samp{Cancel-Lock} is inserted in news posting. It is -used to determine if you wrote a article or not (for cancelling and +used to determine if you wrote an article or not (for cancelling and superseding). Gnus generates a random password string the first time you post a message, and saves it in your @file{~/.emacs} using the Custom system. While the variable is called @code{canlock-password}, it is not @@ -24619,7 +24619,7 @@ This is supposedly what USEFOR wanted to migrate to. See @code{gnus-group-name-charset-method-alist} for customization. @item -The nnml and nnfolder backends store marks for each groups. +The nnml and nnfolder back ends store marks for each groups. This makes it possible to take backup of nnml/nnfolder servers/groups separately of @file{~/.newsrc.eld}, while preserving marks. It also diff --git a/texi/gnus.texi b/texi/gnus.texi index f76bb42..6e1fa4d 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -15953,7 +15953,7 @@ Unlike Parmenides the @acronym{IMAP} designers has decided that things that doesn't exist actually does exist. More specifically, @acronym{IMAP} has this concept of marking articles @code{Deleted} which doesn't actually delete them, and this (marking them @code{Deleted}, that is) is what -nnimap does when you delete a article in Gnus (with @kbd{B DEL} or +nnimap does when you delete an article in Gnus (with @kbd{B DEL} or similar). Since the articles aren't really removed when we mark them with the @@ -18184,7 +18184,7 @@ Creating/deleting nnimap groups when unplugged. Technical note: the synchronization algorithm does not work by ``pushing'' all local flags to the server, but rather incrementally update the server view of flags by changing only those flags that were changed by -the user. Thus, if you set one flag on a article, quit the group and +the user. Thus, if you set one flag on an article, quit the group and re-select the group and remove the flag; the flag will be set and removed from the server when you ``synchronize''. The queued flag operations can be found in the per-server @code{flags} file in the Agent @@ -25216,7 +25216,7 @@ the valid values. Gnus supports Cancel Locks in News. This means a header @samp{Cancel-Lock} is inserted in news posting. It is -used to determine if you wrote a article or not (for cancelling and +used to determine if you wrote an article or not (for cancelling and superseding). Gnus generates a random password string the first time you post a message, and saves it in your @file{~/.emacs} using the Custom system. While the variable is called @code{canlock-password}, it is not