all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: guix-devel@gnu.org
Subject: Re: [RFC] Cosmetic changes to define-configuration usage
Date: Tue, 28 Mar 2023 10:20:30 -0600	[thread overview]
Message-ID: <tvv44e$afu$1@ciao.gmane.io> (raw)
In-Reply-To: <f602cbf8-bdee-0123-fd98-effceffd89c2@makinata.eu>

On 3/24/23 6:33 AM, Bruno Victal wrote:

> I'd like to propose for field specifications in define-configuration to be separated with a
> blank line between them. Reason for this is that it makes it much easier on the eyes
> to read, rather than being presented with a dense hunk of text to sift through.
> 
> I tend to always insert these blank lines when making changes in these parts to aid reading,
> even if they weren't originally present and were not planned to be committed. I'd be happy if
> I could simply keep the line separations and avoid the tedious insert-erase ritual.
> 
> I think I'm not alone in this opinion, consider the following snippets:

It's funny how sometimes this works out. I was just hacking on a 
service's configuration and had the same thought. I had spaced 
everything out so that it wasn't as overwhelming, and with a sigh 
grouped it all back together because that's how all existing services work.

I would definitely appreciate this change in the style standard.

--
Katherine



  reply	other threads:[~2023-03-28 16:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 12:33 [RFC] Cosmetic changes to define-configuration usage Bruno Victal
2023-03-28 16:20 ` Katherine Cox-Buday [this message]
2023-03-31 14:46 ` Maxim Cournoyer
2023-04-03 14:13   ` Bruno Victal
2023-04-08 19:55     ` Maxim Cournoyer

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='tvv44e$afu$1@ciao.gmane.io' \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.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.