Subject: bug#17468: closed (Re: bug#17468: Perl modules)

From: [email-masked] (GNU bug Tracking System)
Date: Mon, 11 Aug 2014 16:39:04 +0000

Your bug report

#17468: fill-paragraph vs. line endings

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
17468: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17468
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#17468: Perl modules
From: [email-masked] (Ludovic Courtès)
To: Andreas Enge <[email-masked]>
Cc: [email-masked], [email-masked]
Date: Mon, 11 Aug 2014 18:37:57 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Fixed in 3a09e1d, which will be in 0.8.

Ludo’.

Subject: Re: Perl modules
From: [email-masked] (Ludovic Courtès)
To: Andreas Enge <[email-masked]>
Cc: [email-masked], [email-masked]
Date: Sun, 11 May 2014 21:16:19 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

Andreas Enge <[email-masked]> 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’.