From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Position of point in reply-with-original
Date: Thu, 03 Feb 2011 23:25:29 +0100 [thread overview]
Message-ID: <874o8kiwme.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87k4hhniw6.fsf@gmail.com>
On Thu, Feb 03 2011, Antoine Levitt wrote:
> There's message-cite-reply-above that does the trick, but is incredibly
> condescending by
>
> - insulting you for wanting the option in the first place in the
> docstring
I think the doc string (I wrote it, as well as the code) is neither
condescending nor insulting:
,----[ <f1> v message-cite-reply-above RET ]
| message-cite-reply-above is a variable defined in `message.el'.
| Its value is nil
|
| Documentation:
| If non-nil, start own text above the quote.
|
| Note: Top posting is bad netiquette. Don't use it unless you
| really must. You probably want to set variable only for specific
| groups, e.g. using `gnus-posting-styles':
|
| (eval (set (make-local-variable 'message-cite-reply-above) t))
|
| This variable has no effect in news postings.
`----
> - ignoring the setting in news posting
That's a feature.
> - asking you if you're really really sure when you post
>
> It seems it's pretty standard use in mail,
Yes unfortunately, like HTML, missing line breaks, stupid disclaimers,
"Sent from my whatever...", signatures without a separator, ...
> and almost all "modern" clients (webmails, thunderbird, outlook and
> such) have this as default.
If you want , use it.
> I'm not trying to start a flamewar as to which one is better, but we
> should give the users the option.
You have the option, as you already discovered.
On Thu, Feb 03 2011, Antoine Levitt wrote:
> 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.
Not true.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2011-02-03 22:25 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
2011-03-15 16:15 ` Lars Magne Ingebrigtsen
2011-02-03 22:25 ` Reiner Steib [this message]
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=874o8kiwme.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).