From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Maxime Devos <maximedevos@telenet.be>, 56297@debbugs.gnu.org
Subject: bug#56297: Guix style imperfections
Date: Wed, 29 Jun 2022 12:20:15 +0200 [thread overview]
Message-ID: <4de77339747298c76370c2a78ee7e0944a39078b.camel@ist.tugraz.at> (raw)
In-Reply-To: <754b54482ba7e443c587230b33ac56416f2b1eb9.camel@telenet.be>
Am Mittwoch, dem 29.06.2022 um 12:18 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op wo 29-06-2022 om 12:15 [+0200]:
> > Here, it depends. I think I'd write this as
> >
> > (native-inputs
> > (modify-inputs (package-native-inputs guile-3.0)
> > (prepend autoconf automake libtool
> > flex gperf
> > gnu-gettext texinfo)))
>
> FWIW, I was thinking of
>
> (native-inputs
> (modify-inputs [...]
> (prepend autoconf
> automake
> libtool
> flex gperf
> gnu-gettext
> texinfo)))
>
> , I haven't really thought about putting multiple inputs on a single
> line myself.
That ought to be the strict suggestion; the variant I posted above
should simply be seen as "acceptable" in lax mode for not breaking the
horizontal space limit.
next prev parent reply other threads:[~2022-06-29 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 9:33 bug#56297: Guix style imperfections Maxime Devos
2022-06-29 10:15 ` Liliana Marie Prikler
2022-06-29 10:18 ` Maxime Devos
2022-06-29 10:20 ` Liliana Marie Prikler [this message]
2022-06-29 10:19 ` Maxime Devos
2022-06-29 10:25 ` Liliana Marie Prikler
2022-07-02 10:11 ` Ludovic Courtès
2022-07-04 21:41 ` Ludovic Courtès
2022-07-19 13:40 ` Maxime Devos
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=4de77339747298c76370c2a78ee7e0944a39078b.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56297@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).