From: Teemu Likonen <tlikonen@iki.fi>
To: Mark Simpson <verdammelt@gmail.com>
Cc: ding@gnus.org
Subject: Re: text/plain with 80 char wrap vs the flowed mime-type (whatever it is)
Date: Thu, 04 Feb 2016 16:30:53 +0200 [thread overview]
Message-ID: <874mdozgwy.fsf@iki.fi> (raw)
In-Reply-To: <874mdp834v.fsf@iki.fi> (Teemu Likonen's message of "Thu, 04 Feb 2016 07:18:24 +0200")
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Teemu Likonen [2016-02-04 07:18:24+02] wrote:
> I've noticed the same but it's probably easy to fix. One could
> add a
> function to gnus-message-setup-hook variable. The function would
> look
> for any "^>" lines (as in regexp) in the message body, go to the
> end of
> line and add text property HARD to value T. I haven't tested
> this idea,
> though.
I meant code like this:
(add-hook 'gnus-message-setup-hook #'tl-format-flowed)
(defun tl-format-flowed ()
(use-hard-newlines nil 'always)
(save-excursion
(message-goto-body)
(save-match-data
(while (re-search-forward "^>.*$" nil t)
(put-text-property (point) (1+ (point)) 'hard t)))))
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-02-04 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:59 Wes Hardaker
2016-01-28 1:52 ` Jorge A. Alfaro-Murillo
2016-02-02 18:22 ` Wes Hardaker
2016-02-04 2:54 ` Mark Simpson
2016-02-04 5:18 ` Teemu Likonen
2016-02-04 14:30 ` Teemu Likonen [this message]
2016-02-05 0:21 ` Mark Simpson
2016-02-05 17:13 ` Jorge A. Alfaro-Murillo
2016-02-04 16:17 ` Nikolaus Rath
2016-02-04 22:41 Magnus Henoch
2016-02-05 0:14 ` Nikolaus Rath
2016-02-05 0:22 ` Mark Simpson
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=874mdozgwy.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=ding@gnus.org \
--cc=verdammelt@gmail.com \
/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).