all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Perl modules
Date: Sun, 11 May 2014 13:31:12 +0200	[thread overview]
Message-ID: <87ppjksgan.fsf@gnu.org> (raw)
In-Reply-To: <20140511103053.GA2361@debian> (Andreas Enge's message of "Sun, 11 May 2014 12:30:53 +0200")

Andreas Enge <andreas@enge.fr> skribis:

> Thanks for the comments, all implemented and pushed.

Thanks!

> On Sun, May 11, 2014 at 11:54:02AM +0200, Ludovic Courtès wrote:
>> Also, two spaces after end-of-sentence periods.
>
> Just as a side note (side-note? sidenote?), in texinfo an end of sentence
> period immediately followed by a line break is interpreted as such (with a
> double space in the info browser), while in the string in the description
> field of our package definitions it is not. So there one should not end
> a line with a period.

But there’s no tool that really “interprets” of what’s in the
‘description’ field[*].  What do you mean?

Ludo’.

[*] Actually, ‘fill-paragraph’ from (guix ui), which is used for the
    output of ‘guix package --search’ does some very basic
    interpretation.

  reply	other threads:[~2014-05-11 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-11  8:56 Perl modules Andreas Enge
2014-05-11  9:20 ` John Darrington
2014-05-11  9:34   ` Andreas Enge
2014-05-11  9:54 ` Ludovic Courtès
2014-05-11 10:30   ` Andreas Enge
2014-05-11 11:31     ` Ludovic Courtès [this message]
2014-05-11 11:41       ` Andreas Enge
2014-05-11 19:16         ` Ludovic Courtès
2014-08-11 16:37           ` bug#17468: " Ludovic Courtès
2014-08-11 16:37           ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2013-12-06 22:17 Andreas Enge
2013-12-06 22:56 ` Ludovic Courtès
2013-12-07 20:24   ` Andreas Enge

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=87ppjksgan.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.