From: Antoine Levitt <antoine.levitt@gmail.com>
To: ding@gnus.org
Subject: Re: Position of point in reply-with-original
Date: Wed, 09 Mar 2011 12:14:28 +0100 [thread overview]
Message-ID: <87k4g84kbv.fsf@gmail.com> (raw)
In-Reply-To: <m3mxl9anda.fsf@quimbies.gnus.org>
05/03/11 11:10, Lars Magne Ingebrigtsen
> Antoine Levitt <antoine.levitt@gmail.com> writes:
>
>> It's done, you can merge the patch if you want.
>
> Great; applied.
>
> Could you also send a patch for message.texi to document this?
Hmm, it seems my reply never made it to the list, not sure why. Here it
is:
I'm not sure what the convention is for the docs, so I opted for a
slightly higher-level description of what the variable does, rather than
the more technical info in C-h v.
diff --git a/doc/misc/message.texi b/doc/misc/message.texi
index b286399..9914235 100644
--- a/doc/misc/message.texi
+++ b/doc/misc/message.texi
@@ -1930,6 +1930,26 @@ posting a prepared news message.
@section Insertion Variables
@table @code
+
+@item message-cite-style
+@vindex message-cite-style
+The overall style to be used when replying to messages. This controls
+things like where the reply should be put relative to the original,
+how the citation is formatted, where the signature goes, etc.
+
+Value is either @code{nil} (no variable overrides) or a let-style list
+of pairs @code{(VARIABLE VALUE)} to override default values.
+
+See @code{gnus-posting-styles} to set this variable for specific
+groups. Presets to impersonate popular mail agents are available in the
+@code{message-cite-style-*} variables.
+
+@item message-cite-reply-position
+@vindex message-cite-reply-position
+Where the reply should be positioned. Available styles are
+@code{traditional} to reply inline, @code{above} for top-posting, and
+@code{below} for bottom-posting
+
@item message-ignored-cited-headers
@vindex message-ignored-cited-headers
All headers that match this regexp will be removed from yanked
next prev parent reply other threads:[~2011-03-09 11:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:46 Antoine Levitt
2011-02-03 16:24 ` Eric Abrahamsen
2011-02-03 17:10 ` Antoine Levitt
2011-02-03 17:31 ` Adam Sjøgren
2011-02-03 19:18 ` Steinar Bang
2011-02-03 21:52 ` Antoine Levitt
2011-02-03 22:10 ` Adam Sjøgren
2011-02-03 22:29 ` Antoine Levitt
2011-02-03 22:47 ` Ted Zlatanov
2011-02-04 8:45 ` Lars Ingebrigtsen
2011-02-04 9:38 ` Antoine Levitt
2011-02-04 18:25 ` Ted Zlatanov
2011-02-04 18:46 ` Lars Ingebrigtsen
2011-02-05 17:01 ` Steinar Bang
2011-02-05 19:43 ` Peter Münster
2011-02-19 15:13 ` Antoine Levitt
2011-02-20 1:51 ` Lars Ingebrigtsen
2011-02-21 9:26 ` Antoine Levitt
2011-02-21 9:35 ` Lars Ingebrigtsen
2011-03-04 14:12 ` Antoine Levitt
2011-03-05 10:10 ` Lars Magne Ingebrigtsen
2011-03-09 11:14 ` Antoine Levitt [this message]
2011-03-15 16:15 ` Lars Magne Ingebrigtsen
2011-02-03 22:25 ` Reiner Steib
2011-02-03 22:33 ` Antoine Levitt
2011-02-03 22:41 ` Steinar Bang
2011-02-04 9:21 ` Peter Münster
2011-02-03 22:40 ` Ted Zlatanov
2011-02-04 8:46 ` Lars Ingebrigtsen
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=87k4g84kbv.fsf@gmail.com \
--to=antoine.levitt@gmail.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).