From: Uwe Brauer <oub@mat.ucm.es>
To: info-gnus-english@gnu.org
Subject: Re: problems with the news-reply-hook and the message-setup-hook
Date: Mon, 19 Nov 2007 15:23:29 +0100 [thread overview]
Message-ID: <87tznipb4u.fsf@mat.ucm.es> (raw)
In-Reply-To: <v9ve81yqj5.fsf@marauder.physik.uni-ulm.de>
>>>>> "Reiner" == Reiner Steib <reinersteib+gmane@imap.cc> writes:
> In No Gnus, there is `message-cite-reply-above', but it's doc string
> says "This variable has no effect in news postings."
Well I am using no gnus 0.6 and can't find this variable so it must be
new.
>> and one has almost to apologise for using *bottom posting* or
>> *inline replying*.
>> Now that function I have defined interactively and in this way I can
>> call it, however I would find it more convenient to have it in a
>> hook, so that I don't have to call the function explicitly however I
>> put it in the news-reply-hook
> There's no such hook in Gnus, AFAICS.
>> and in the message-setup-hook without any result. Can anybody give
>> me an idea?
> Maybe setting `message-citation-line-format' (new in No Gnus,
> cf. `message-insert-formatted-citation-line') specially for these
> groups?
The problem is that starts with a
>>>> or something similar,
besides it is not flexible enough and it is not connected to
bbdb. The idea I had was that such a string is configured according
to a relevant entry in the bbdb.
> When using `message-setup-hook' you need to make sure to jump to the
> right position in the message buffer: `message-goto-body', ...
I have the feeling that it there is a conflict with supercite, like
supercite inserts its stuff first and then my bbdbcite command is not
executed.
Uwe
next prev parent reply other threads:[~2007-11-19 14:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 18:18 Uwe Brauer
2007-11-17 13:01 ` Reiner Steib
2007-11-19 14:23 ` Uwe Brauer [this message]
2007-11-19 18:19 ` Reiner Steib
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=87tznipb4u.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=info-gnus-english@gnu.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).