From: SL Baur <steve@xemacs.org>
Subject: Re: Quassia Gnus v0.17 is released
Date: 26 Nov 1997 11:10:15 -0800 [thread overview]
Message-ID: <m2hg8z4gko.fsf@altair.xemacs.org> (raw)
In-Reply-To: Stefan Waldherr's message of "26 Nov 1997 12:38:57 -0500"
> @usit is not handled by texinfo
1997-11-26 SL Baur <steve@altair.xemacs.org>
* message.texi (Insertion): Fix typo.
(Responses): Ditto.
(Reply): Ditto.
===================================================================
RCS file: texi/RCS/message.texi,v
retrieving revision 1.15
diff -u -r1.15 texi/message.texi
--- texi/message.texi 1997/11/26 18:56:27 1.15
+++ texi/message.texi 1997/11/26 19:06:52
@@ -140,7 +140,7 @@
@vindex message-reply-to-function
Message uses the normal methods to determine where replies are to go
-(@pxref{Responding}), but you can change the behavior to suit your needs
+(@pxref{Responses}), but you can change the behavior to suit your needs
by fiddling with the @code{message-reply-to-function} variable.
If you want the replies to go to the @code{Sender} instead of the
@@ -441,7 +441,7 @@
that look like:
@example
-Hallvard B Furuseth <h.b.furuseth@usit.uio.no> writes:
+Hallvard B Furuseth <h.b.furuseth@@usit.uio.no> writes:
@end example
Point will be at the beginning of the body of the message when this
@@ -1204,7 +1204,7 @@
To determine where a message is to go, the following algorithm is used
by default.
-@table @def
+@table @dfn
@item reply
A @dfn{reply} is when you want to respond @emph{just} to the person who
sent the message via mail. There will only be one recipient. To
@@ -1224,7 +1224,7 @@
following headers will be concatenated to form the outgoing
@code{To}/@code{Cc} headers:
-@table
+@table @code
@item From
(unless there's a @code{Reply-To}, in which case that is used instead).
prev parent reply other threads:[~1997-11-26 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-26 16:43 Lars Magne Ingebrigtsen
1997-11-26 17:38 ` Stefan Waldherr
1997-11-26 19:10 ` SL Baur [this message]
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=m2hg8z4gko.fsf@altair.xemacs.org \
--to=steve@xemacs.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).