From 536edad9d501b68bb8e201ce8302758723c80c31 Mon Sep 17 00:00:00 2001 From: Simon Josefsson Date: Tue, 13 May 2003 08:11:52 +0000 Subject: [PATCH] (IMAP, Agent and IMAP, Oort Gnus): s/a/an/. Tiny patch from Niklas Morberg . --- texi/ChangeLog | 5 +++++ texi/gnus.texi | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/texi/ChangeLog b/texi/ChangeLog index 3ac2e82a0..6b7f1063a 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.texi b/texi/gnus.texi index e21dee754..cf6b160bd 100644 --- a/texi/gnus.texi +++ b/texi/gnus.texi @@ -15952,7 +15952,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 @@ -18183,7 +18183,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 @@ -25202,7 +25202,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 -- 2.25.1