From: Satoshi Yoshida <dynamisxar@icloud.com>
To: info-gnus-english@gnu.org
Subject: Re: Strip signature on reply without standard separator
Date: Wed, 24 Aug 2022 11:30:36 +0900 [thread overview]
Message-ID: <87bksaz837.fsf@icloud.com> (raw)
In-Reply-To: <87zggbz3ho.fsf@icloud.com> (Satoshi Yoshida's message of "Thu, 11 Aug 2022 15:41:23 +0900")
Satoshi Yoshida <dynamisxar@icloud.com> writes:
> I solved it by customizing mu-cite.el from melpa in reference to
> http://roguelife.org/~tsumura/emacs/mu-cite.html
> https://pc11.5ch.net/test/read.cgi/unix/1114097161/
[...]
> But I have a concern. When I compose a message,
> a blank line occurs on biginning of buffer. I can't block it.
Fixed.
(setq mu-cite-prefix-format '("> "))
(setq mu-cite-cited-prefix-regexp "\\(^[^ \t\n<>]+>+[ \t]*\\)")
(setq mu-cite-top-format '(from " writes:\n\n"))
(add-hook 'mu-cite-post-cite-hook
'(lambda ()
(save-excursion
(save-excursion
(goto-char (point-min))
(replace-regexp "^> >" ">>")
(goto-char (point-min))
(replace-regexp "^> -- .*\n\\(>.*\n\\)*" "")
(goto-char (point-min))
(replace-regexp "^\\(>[ \t]+\n\\)+> \\(best\
\\( regards\\| wishes\\)?\\|cheers\\|\\(good\\)?bye\\|good luck\
\\|\\(kind \\|warm\\(est\\)? \\)?regards\\|respectfully\\|\
\\(yours \\)?sincerely\\( yours\\)?\\|thank you\\( very much\\)?\
\\|\\(many \\)?thanks\\( in advance\\| very much\\)?\\),[ \t]*\n\
\\(>.*\n\\)*" "")
(goto-char (point-min))
(replace-regexp "^\\(>[ \t]+\n\\)+> [ \t]*\
\\(-+[ \t]*\\)?[a-zA-Z]+[ \t]*\n\\(>[ \t]+\n\\)*\n-- " "\n-- ")
(goto-char (point-min))
(replace-regexp "^\\(>[> \t]+\n\\)+\n-- " "\n-- "))
(goto-line 1)
(delete-blank-lines))))
--
Satoshi Yoshida
next prev parent reply other threads:[~2022-08-24 2:30 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
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 [this message]
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=87bksaz837.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).