From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: ding@gnus.org
Subject: Re: What's the best way to auto-sign some emails but not all?
Date: Tue, 03 Dec 2024 12:35:55 +0200 [thread overview]
Message-ID: <871pypjbp0.fsf@> (raw)
In-Reply-To: <874j3mdsr7.fsf@miraculix.mork.no> (=?utf-8?Q?=22Bj=C3=B8rn?= Mork"'s message of "Mon, 02 Dec 2024 16:11:40 +0100")
Bjørn Mork <bjorn@mork.no> writes:
> Thanks for all the great ideas. I have realized that there are probably
> more ways to do this than there are Gnus users :-)
>
> The discussion made me look closer at the code in question, which I
> should have done in the first place. And I believe my problem is that
> there are no hooks in the appropriate places. Yanking the original
> message happens very late, long after message-setup is finished.
>
> Most of the suggestions depend on message-setup-hook in some way, making
> them work and fail similar to my existing gnus-posting-styles setup. One
> exception is gnus-alias which AFAIU can apply a new identity to an
> existing message buffer. But that's an interactive choice, which is
> what I'm trying to avoid.
That is not true. gnus-alias has rules which make it possible to
automatically apply an identity. Check C-h v gnus-alias-identity-rules RET.
Message-signature manual or automatically should also take into account
a yanked article AFAIU.
next prev parent reply other threads:[~2024-12-03 10:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:49 Bjørn Mork
2024-11-30 18:29 ` Trevor Arjeski
2024-11-30 19:28 ` Bjørn Mork
2024-11-30 20:17 ` Trevor Arjeski
2024-12-02 15:11 ` Bjørn Mork
2024-12-03 10:35 ` Björn Bidar [this message]
2024-12-03 11:36 ` Bjørn Mork
2024-12-03 20:38 ` Björn Bidar
2024-12-01 3:58 ` Sean Whitton
2024-12-01 23:04 ` Björn Bidar
2024-12-01 23:43 ` Bob Newell
2024-12-08 5:05 ` James Thomas
2024-12-08 13:22 ` Bjørn Mork
2024-12-08 21:03 ` James Thomas
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=871pypjbp0.fsf@ \
--to=bjorn.bidar@thaodan.de \
--cc=bjorn@mork.no \
--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).