unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
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:25:04 +0200	[thread overview]
Message-ID: <2a8343542ee2301f3effe1cdb04a121c180c119f.camel@ist.tugraz.at> (raw)
In-Reply-To: <473413ef0e01f1dcc7d62602a5b660230b216282.camel@telenet.be>

Am Mittwoch, dem 29.06.2022 um 12:19 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op wo 29-06-2022 om 12:15 [+0200]:
> > > >                                     (delete-file
> > > >                                      "test-
> > > > suite/tests/version.test")
> > > > #t))))))
> > > 
> > > (Would be nice if "guix style" could be taught to remove those
> > > #t,
> > > but
> > > that seems more a feature limitation than a bug to me.)
> > It can still do better by not contracting them imho.
> 
> TBC, do you mean doing #t -> #true, #f -> #false?
I mean leaving them on an extra line.  The current style tool mostly
errs when contracting multiple lines, which imho should not be its
task.

The problem that is solved here, is that people sometimes (particularly
in the uri field of the source) make these contractions for style
reasons.  Guix style, having been taught that, tries to extrapolate
this to all fields.

Cheers





  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
2022-06-29 10:19   ` Maxime Devos
2022-06-29 10:25     ` Liliana Marie Prikler [this message]
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=2a8343542ee2301f3effe1cdb04a121c180c119f.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).