From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Message mangled
Date: Mon, 31 Jan 2011 18:37:13 -0800 [thread overview]
Message-ID: <87vd14xyxy.fsf@gnus.org> (raw)
In-Reply-To: <871v3s6cl0.fsf@gnu.org>
ludo@gnu.org (Ludovic Courtès) writes:
> It’s <92164B15-45D1-4D76-9AF6-8E1E098C04BD@telia.com>, also at
It is flow-fill that's doing this... but not the parts you'd think.
If you eval the following in a Gnus article buffer:
(progn
(setq buffer-read-only nil)
(insert "gcc parser.o lexer.o driver.o guile++.o guile.o exception.o tuple.o `guile-config link` -lstdc++ -o guile++\n")
(forward-line -1)
(let ((fill-prefix nil)
(fill-column (eval fill-flowed-display-column))
filladapt-mode
adaptive-fill-mode)
(fill-region (point-at-bol)
(min (1+ (point-at-eol))
(point-max))
'left 'nosqueeze)))
Then the ` before "guile-config" will disappear.
Anybody got any ideas why fill-region would do that?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-02-01 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 10:26 Ludovic Courtès
2011-01-27 23:51 ` Lars Ingebrigtsen
2011-01-28 19:26 ` Andreas Schwab
2011-01-28 22:11 ` Lars Ingebrigtsen
2011-01-31 20:30 ` Ludovic Courtès
2011-02-01 2:37 ` Lars Ingebrigtsen [this message]
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=87vd14xyxy.fsf@gnus.org \
--to=larsi@gnus.org \
--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).