Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Position of point in reply-with-original
Date: Thu, 03 Feb 2011 11:24:46 -0500	[thread overview]
Message-ID: <87r5bpgk6p.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87tyglxjja.fsf@gmail.com>

On Thu, Feb 03 2011, Antoine Levitt wrote:

> Hello,
>
> This might be a very dumb question but I didn't find any posts or doc to
> that effect. When I reply-with-original, the point is in weird
> places. For instance,
>
> *headers*
> --text follows this line--
> On XX, YY wrote
> !> stuff
>
> with point at !. Why isn't it either above or below by default, and why
> isn't there a variable to change this behaviour? I'd expect this issue
> to have been raised by now: how do people cope with this?

I started a thread on this issue either here or in emacs.gnus.user
pretty recently, but now can't find it… Basically the variable
message-citation-line-function dictates what kind of citation line is
inserted, and where point ends up afterwards. All the built-in defaults
for that variable do what you've seen: place point after the citation
line. If you want open space *above* the citation line, and start point
at the top of the buffer, you'll have to write a custom function. Check
out section 3.6 of the info manual for Message (how do you all make
nifty clickable links to Info nodes, by the way?).

Briefly, the "interleaved" quotation style expects that you'd begin
composing your reply somewhere down in the midst of the quoted text.
"Top posting" style expects you to start typing a distinct reply at the
top of the message body. Gnus, having evolved for newsreading, assumes
you don't want to top-post.

Eric




  reply	other threads:[~2011-02-03 16:24 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 [this message]
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
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=87r5bpgk6p.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).