Gnus development mailing list
 help / color / mirror / Atom feed
From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: Position of point in reply-with-original
Date: Thu, 03 Feb 2011 23:10:35 +0100	[thread overview]
Message-ID: <87pqr8py5g.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87pqr8946o.fsf@gmail.com>

On Thu, 03 Feb 2011 22:52:15 +0100, Antoine wrote:

>>> I'm not trying to start a flamewar as to which one is better, but we
>>> should give the users the option.

>> Why?

> I don't know, somehow I was under the impression that gnus was
> customizable :)

Me too. You didn't quite answer the question, though?

>> I don't understand why you wouldn't want people to jump through hoops
>> to do the - arguably - wrong thing? It is entirely possible to do so,
>> but why make it easier?

> Wow, I wasn't really expecting to get this kind of answer on the gnus
> ML.

Sorry to disappoint you so. Apparantly the group isn't as homogeneous as
expected.

> I haven't given much thought as to the different posting styles, and
> am not going to enter the debate. But I for one would like to post
> above the cited text, at least in mail. In the current state of
> affairs, I cannot do it without modifying gnus' source code.

You're not going to enter the debate, but on the other hand you want it
to work your way. Sounds kind of self-contradictory to me.

Anyway, I think you could do exactly what you want by adding a hook
rather than modifying the source code of Gnus.

Perhaps message-setup-hook?


  Best regards,

    Adam

-- 
 "Pray, Mr. Babbage, if you put into the machine wrong        Adam Sjøgren
  figures, will the right answers come out?"             asjo@koldfront.dk




  reply	other threads:[~2011-02-03 22:10 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 [this message]
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
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=87pqr8py5g.fsf@topper.koldfront.dk \
    --to=asjo@koldfront.dk \
    --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).