GNU bug report logs - #17468
fill-paragraph vs. line endings

Previous Next

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas <at> enge.fr>
Cc: guix-devel <at> gnu.org, bug-guix <at> gnu.org
Subject: Re: Perl modules
Date: Sun, 11 May 2014 21:16:19 +0200

Andreas Enge <andreas <at> enge.fr> skribis:

> On Sun, May 11, 2014 at 01:31:12PM +0200, Ludovic Courtès wrote:
>> But there’s no tool that really “interprets” of what’s in the
>> ‘description’ field[*].  What do you mean?
>> [*] Actually, ‘fill-paragraph’ from (guix ui), which is used for the
>>     output of ‘guix package --search’ does some very basic
>>     interpretation.
>
> Well, the output of "guix package --search" has different line breaks than
> those present in the string of the description field. So something modifies
> it,

Yes, that’s ‘fill-paragraph’.

> maybe the scheme interpreter itself in what it does with multi-line
> strings, maybe the function you mention. In any case, "x.\nY" may be
> output as "x. Y"; so if we wish to have double spaces in the output,
> we need to write "x.  Y" on the same line.

That’s really a bug in ‘fill-paragraph’.

I’m filing it now and will look at it later, unless someone beats me.
;-)

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.