From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Lirzin <mthl@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] lint: Check non-translated package descriptions.
Date: Sat, 26 Sep 2015 15:05:28 +0200 [thread overview]
Message-ID: <877fnd49gn.fsf@gnu.org> (raw)
In-Reply-To: <874miikx6f.fsf@openmailbox.org> (Mathieu Lirzin's message of "Fri, 25 Sep 2015 23:26:32 +0200")
Mathieu Lirzin <mthl@openmailbox.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mathieu Lirzin <mthl@openmailbox.org> skribis:
>>
>>> diff --git a/guix/scripts/lint.scm b/guix/scripts/lint.scm
>>> index b0427f7..0adb3bf 100644
>>> --- a/guix/scripts/lint.scm
>>> +++ b/guix/scripts/lint.scm
>>> @@ -146,11 +146,11 @@ monad."
>>> (define (check-texinfo-markup description)
>>> "Check that DESCRIPTION can be parsed as a Texinfo fragment. If the
>>> markup is valid return a plain-text version of DESCRIPTION, otherwise #f."
>>> - (catch 'parser-error
>>> - (lambda () (texi->plain-text description))
>>> - (lambda (keys . args)
>>> - (emit-warning package (_ "Texinfo markup in description is invalid"))
>>> - #f)))
>>> + (unless (false-if-exception (texi->plain-text description))
>>> + (emit-warning package
>>> + (_ "Texinfo markup in description is invalid")
>>> + 'description)
>>> + #f))
>>
>> In general, it’s best to avoid ‘false-if-exception’ because it’s too
>> coarse-grain. Here it’s probably OK though, because we want to catch
>> any error that may occur in during the conversion. So this patch is OK
>> (with appropriate commit log.)
>
> Ok, thanks for the explanation.
>
>
> From 429ff285609120c4135eb64f1d6911924a24f5e6 Mon Sep 17 00:00:00 2001
> From: Mathieu Lirzin <mthl@openmailbox.org>
> Date: Fri, 25 Sep 2015 00:37:36 +0200
> Subject: [PATCH] lint: Improve 'check-texinfo-markup'.
>
> * guix/scripts/lint.scm (check-description-style): Set 'field' parameter
> when emitting a warning in 'check-texinfo-markup'. Catch any error
> that may occur in during the 'texi->plain-text' conversion. This is a
> followup to commit 2748ee3.
OK!
Thanks,
Ludo’.
next prev parent reply other threads:[~2015-09-26 13:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 13:44 [PATCH 0/2] lint: Texinfo again Mathieu Lirzin
2015-09-22 13:44 ` [PATCH 1/2] lint: Check non-translated package descriptions Mathieu Lirzin
2015-09-22 21:36 ` Ludovic Courtès
2015-09-24 23:04 ` Mathieu Lirzin
2015-09-25 16:17 ` Ludovic Courtès
2015-09-25 21:26 ` Mathieu Lirzin
2015-09-26 13:05 ` Ludovic Courtès [this message]
2015-09-26 17:09 ` Mathieu Lirzin
2015-09-27 20:22 ` Ludovic Courtès
2015-09-22 13:44 ` [PATCH 2/2] lint: Accept '`' character Mathieu Lirzin
2015-09-22 21:37 ` Ludovic Courtès
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=877fnd49gn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mthl@openmailbox.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.