From: Satoshi Yoshida <dynamisxar@icloud.com>
To: info-gnus-english@gnu.org
Subject: Re: Strip signature on reply without standard separator
Date: Tue, 09 Aug 2022 17:34:35 +0900 [thread overview]
Message-ID: <87r11plsro.fsf@icloud.com> (raw)
In-Reply-To: <87edxqyn6c.fsf@dataswamp.org> (Emanuel Berg's message of "Tue, 09 Aug 2022 07:56:59 +0200")
Emanuel Berg <incal@dataswamp.org> writes:
> That's probably not the way to do it, I think that, i.e.
> `gnus-signature-separator', should be used only for the
> separator(s) per se and not in order to do other stuff like
> that, since processing is likely to be based on that and what
> you don't want to see last maybe appears in the middle of the
> mail and other such unpredicted (?) situations ...
Hard to say, I want to read whole message (100%) in article buffer.
Just on reply, I want to strip signature without "-- ".
> That kind of stuff you want can be done tho for sure, did you
> check out this chapter:
>
> (info "(gnus) Article Washing")
>
> Have a look at `article-translate-strings',
> `gnus-article-strip-multiple-blank-lines', and
> `gnus-article-prepare-hook' ...
I read info and found `gnus-article-strip-multiple-blank-lines'
and `gnus-article-prepare-hook'.
Additionally, `article-translate-strings' in
https://lists.gnu.org/archive/html/info-gnus-english/2015-05/msg00025.html
Though my understanding is 50%, are these things useful for
washing "sent from my iPhone" (for example) automatically
in article buffer?
> HTH!
Thanks for your assistance.
--
Satoshi Yoshida
next prev parent reply other threads:[~2022-08-09 8:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 4:28 Satoshi Yoshida
2022-08-09 5:56 ` Emanuel Berg
2022-08-09 8:34 ` Satoshi Yoshida [this message]
2022-08-09 8:52 ` Emanuel Berg
2022-08-09 9:25 ` Satoshi Yoshida
2022-09-11 9:46 ` Satoshi Yoshida
2022-09-12 6:45 ` Satoshi Yoshida
2022-09-14 6:08 ` Emanuel Berg
2022-09-14 7:48 ` Satoshi Yoshida
2022-08-11 6:41 ` Satoshi Yoshida
2022-08-11 14:48 ` Satoshi Yoshida
2022-08-12 3:06 ` Satoshi Yoshida
2022-08-11 15:26 ` Satoshi Yoshida
2022-08-24 2:30 ` Satoshi Yoshida
2022-08-24 2:37 ` Emanuel Berg
2022-08-24 3:55 ` Satoshi Yoshida
2022-08-24 5:28 ` Emanuel Berg
2022-08-24 22:26 ` Michael Heerdegen
2022-08-25 2:10 ` Satoshi Yoshida
2022-08-25 3:04 ` Strip signature on reply without standard separator [solved] Satoshi Yoshida
2022-08-25 6:46 ` Emanuel Berg
2022-08-27 6:59 ` Strip signature on reply without standard separator Satoshi Yoshida
2022-08-27 7:19 ` Satoshi Yoshida
2022-09-04 0:48 ` Satoshi Yoshida
2022-09-04 2:04 ` Emanuel Berg
2022-09-06 23:36 ` Satoshi Yoshida
2022-09-07 1:14 ` Emanuel Berg
2022-09-15 23:50 ` Satoshi Yoshida
2022-09-19 0:58 ` Emanuel Berg
2022-09-21 9:15 ` Satoshi Yoshida
2022-09-21 13:15 ` Emanuel Berg
2022-09-23 21:36 ` Satoshi Yoshida
2022-09-24 15:29 ` Emanuel Berg
2022-09-25 3:32 ` Satoshi Yoshida
2022-09-25 3:41 ` Emanuel Berg
2022-09-26 8:03 ` Satoshi Yoshida
2022-09-26 12:28 ` Emanuel Berg
2022-10-22 6:16 ` Satoshi Yoshida
2022-10-23 23:45 ` Emanuel Berg
2022-09-25 9:42 ` Michael Heerdegen
2022-09-26 7:56 ` Satoshi Yoshida
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=87r11plsro.fsf@icloud.com \
--to=dynamisxar@icloud.com \
--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).