Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Position of point in reply-with-original
Date: Fri, 04 Feb 2011 00:45:53 -0800	[thread overview]
Message-ID: <87vd10kx1a.fsf@gnus.org> (raw)
In-Reply-To: <87d3n8loqz.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> I agree with the defvar -> defcustom change.
>
> I think the top-posting setup should be a little more involved,
> mirroring Outlook somewhat.  This is what I use (I got help from the
> Gnus mailing list when I set it up):
>
> ;; outlooky
> (defun sc-style-outlook ()
>   (interactive)
>   (setq
>    message-cite-function 'message-cite-original
>    message-citation-line-function 'message-insert-formatted-citation-line
>    message-cite-reply-above 'is-evil
>    message-yank-prefix ""
>    message-yank-cited-prefix ""
>    message-yank-empty-prefix ""
>    message-citation-line-format
>    "\n\n-----------------------\nOn %a, %b %d %Y, %N wrote:\n"))

Given that this much is needed to get a satisfactory top posting format,
I don't think making the defvar->defcustom change would help much.

Perhaps there should be a new meta-ish variable, say

(defcustom message-cite-style nil
  "The overall style to be used when yanking cited text.
Values are either `traditional' (cited text first),
`top-post' (cited text at the bottom), or nil (don't override the
individual message variables)."
  :version "24.1"
  :group 'message-various
  :type '(choice (const :tag "None" :value nil)
		 (const :tag "Traditional" :value traditional)
		 (const :tag "Top-post" :value top-post)))

This would bind the variables you mention above if set to `traditional'
or `top-post'.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2011-02-04  8:45 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 [this message]
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
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=87vd10kx1a.fsf@gnus.org \
    --to=larsi@gnus.org \
    --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).