From: Reiner Steib <4uce.02.r.steib@gmx.net>
Subject: Re: Drafts feature-request/bug.
Date: Wed, 11 Sep 2002 18:19:52 +0200 [thread overview]
Message-ID: <v94rcwcxcn.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <vafu1kwx2kj.fsf@lucy.cs.uni-dortmund.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1855 bytes --]
--=-=-=
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
On Wed, Sep 11 2002, Kai Großjohann wrote:
> (<self-advertisement> And then, there is nndraft:delayed or somesuch
> for delayed articles. </self-advertisement>)
Kai, you should advertise this more often. I missed this up to now. ;-)
Reading the manual section, I found a typo and saw that there's no
"summary line" (r.h.s. in <info://gnus/Top>):
--=-=-=
Content-Type: text/x-patch
Content-Disposition: inline; filename=gnus.texi.gnus-delay.patch
Content-Description: Typo and missing summary for Delayed Articles
--- gnus.texi.~6.319.~ Wed Sep 11 11:51:19 2002
+++ gnus.texi Wed Sep 11 17:08:32 2002
@@ -499,7 +499,7 @@
* Choosing Articles:: Reading articles.
* Paging the Article:: Scrolling the current article.
* Reply Followup and Post:: Posting articles.
-* Delayed Articles::
+* Delayed Articles:: Delaying the sending of a message.
* Marking Articles:: Marking articles as read, expirable, etc.
* Limiting:: You can limit the summary buffer.
* Threading:: How threads are made.
@@ -5405,7 +5405,7 @@
(months) and @code{Y} (years).
@item
-A specific date. Looks like @code{YYYYY-MM-DD}. The message will be
+A specific date. Looks like @code{YYYY-MM-DD}. The message will be
delayed until that day, at a specific time (eight o'clock by default).
See also @code{gnus-delay-default-hour}.
--=-=-=
Concerning the argument `no-keymap' in `gnus-delay-initialize': the
description in the manual doesn't match the doc-string and
implementation in `gnus-delay.el'
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
--=-=-=--
next prev parent reply other threads:[~2002-09-11 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 23:19 Scott A Crosby
2002-09-11 10:06 ` Kai Großjohann
2002-09-11 10:19 ` Scott A Crosby
2002-09-11 11:09 ` Kai Großjohann
2002-09-11 16:19 ` Reiner Steib [this message]
2002-09-11 16:35 ` Kai Großjohann
2002-09-11 18:44 ` charset problems with gnus-delay (was: Drafts feature-request/bug.) Reiner Steib
2002-09-11 19:41 ` charset problems with gnus-delay Reiner Steib
2002-09-12 9:50 ` charset problems with gnus-delay (was: Drafts feature-request/bug.) Kai Großjohann
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=v94rcwcxcn.fsf@marauder.physik.uni-ulm.de \
--to=4uce.02.r.steib@gmx.net \
--cc=reiner.steib@gmx.de \
/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).