From: "Ludovic Courtès" <ludo@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 38436@debbugs.gnu.org
Subject: [bug#38436] [PATCH] gnu: Add gfortran-toolchain
Date: Thu, 12 Dec 2019 14:20:54 +0100 [thread overview]
Message-ID: <87wob17k95.fsf@gnu.org> (raw)
In-Reply-To: <m1immm38jy.fsf@ordinateur-de-catherine--konrad.home> (Konrad Hinsen's message of "Wed, 11 Dec 2019 21:34:57 +0100")
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
>> xgettext recognizes (synopsis "foo"), but it won’t catch the variables
>> defined above, because they’re not preceded by the ‘synopsis’ keyword or
>> anything.
>
> OK, so what's the exact rule? If the literal string has to be right
> after the symbol "synopsis", then your optional-arg approach shouldn't
> work when the argument is supplied at the call site (in
> gfortran-toolchain).
Good point!
The exact rule is given the the ‘--keyword’ options in
po/packages/Makevars. Namely, xgettext will recognize:
(synopsis "…")
Thus, something like:
(define* (foo #:key (synopsis "…"))
…)
works.
Now, for gfortran, you could resort to a not-so-fancy hack (used in
‘define-word-list-dictionary’ in (gnu packages aspell)) like this:
(let-syntax ((synopsis (syntax-rules () ((_ str) str))))
(make-gcc-toolchain gfortran #:synopsis (synopsis "…")))
Quite an effort for this little thing, but I couldn’t find of anything
simpler.
HTH,
Ludo’.
next prev parent reply other threads:[~2019-12-12 13:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 17:46 [bug#38436] [PATCH] gnu; Add gfortran-toolchain Konrad Hinsen
2019-12-02 15:01 ` [bug#38436] [PATCH] gnu: " Konrad Hinsen
2019-12-09 14:30 ` Ludovic Courtès
2019-12-10 13:11 ` Konrad Hinsen
2019-12-10 14:38 ` Ludovic Courtès
2019-12-11 10:30 ` Konrad Hinsen
2019-12-11 10:30 ` Konrad Hinsen
2019-12-11 11:12 ` Ludovic Courtès
2019-12-11 20:34 ` Konrad Hinsen
2019-12-12 13:20 ` Ludovic Courtès [this message]
2019-12-12 15:19 ` Konrad Hinsen
2019-12-12 21:22 ` Ludovic Courtès
2019-12-13 12:56 ` Konrad Hinsen
2019-12-13 12:53 ` Konrad Hinsen
2019-12-13 12:56 ` Jonathan Brielmaier
2019-12-14 23:22 ` bug#38436: " 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wob17k95.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38436@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).