all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Regarding the vertical alignment in the record definitions
Date: Thu, 05 Dec 2024 08:41:27 +0000	[thread overview]
Message-ID: <62e7cd1811c5514c6dd6e067d712999a@libre.brussels> (raw)
In-Reply-To: <87frn2li0z.fsf@gmail.com>

Hello,

On 2024-12-05 07:13, Maxim Cournoyer wrote:
> Hi Tomas,
> 
> ...
> 
> I agree it's a bit tedious, both manually and also in diffs.  My
> personal preference is to leave just one space between the field name
> and the value, that also holds for variable bounds in lets, etc., to
> avoid the problem (at the cost of some visual clarity, I guess).
> 
> One day maybe we'll have a general tool like 'scheme-fmt' to run on a
> file save hook that'd fix the format question for good, like Python has
> with 'black' or 'ruff', etc.  I have on mind to work on such a tool, 
> but
> it's low in the list.

FWIW, Im slowly cobbling together some parsing-expression-grammars for 
Guix package definitions.
Im doing it in the Lisp TXR atm but Im going to create a hybrid approach 
with Prolog to make it more general.

In addition to outputting a unified formatting, Im planning on altering 
descriptions so that that that content is outputted in the format 
Texinfo.

Please dont expect anything soon but should anybody start any other 
initiative then I may possibly some useful assets or details by then.

Kind regards,


Jonathan


  reply	other threads:[~2024-12-05  8:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  0:34 Regarding the vertical alignment in the record definitions Tomas Volf
2024-12-05  7:13 ` Maxim Cournoyer
2024-12-05  8:41   ` indieterminacy [this message]
2024-12-09  0:31     ` Maxim Cournoyer
2024-12-05  7:35 ` Efraim Flashner

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=62e7cd1811c5514c6dd6e067d712999a@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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.