From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: More on format=flowed
Date: Sun, 02 Jan 2011 20:32:31 +0100 [thread overview]
Message-ID: <m3y673qey8.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <mailman.0.1293983977.14417.info-gnus-english@gnu.org>
Yuri D'Elia <wavexx@users.sf.net> writes:
> (defun harden-newlines ()
> (save-excursion
> (goto-char (point-min))
> (while (search-forward "\n" nil t)
> (put-text-property (1- (point)) (point) 'hard t))))
So, basically, you make all the newlines hard. Isn't the point of
`use-hard-newlines' that you can mix and match hard and soft newlines?
That is:
[...]
> word-wrap t
> use-hard-newlines t))))
You're mixing `use-hard-newlines' with `word-wrap', and the two don't
really mix that well. I think.
(I've never used either.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next parent reply other threads:[~2011-01-02 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1293983977.14417.info-gnus-english@gnu.org>
2011-01-02 19:32 ` Lars Magne Ingebrigtsen [this message]
2011-01-03 0:55 ` Yuri D'Elia
2011-01-02 15:59 Yuri D'Elia
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=m3y673qey8.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--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).