From: Simon Tournier <zimon.toutoune@gmail.com>
To: Bruno Victal <mirai@makinata.eu>, 62000@debbugs.gnu.org
Subject: bug#62000: Inconsistent indentation rules for define-configuration
Date: Tue, 07 Mar 2023 14:16:57 +0100 [thread overview]
Message-ID: <86ilfcbt12.fsf@gmail.com> (raw)
In-Reply-To: <372a5f84-018c-9cee-ba2c-2b564a3d9e31@makinata.eu>
Hi,
Cool you had the number 62000. ;-)
On Mon, 06 Mar 2023 at 12:48, Bruno Victal <mirai@makinata.eu> wrote:
> Suspected file: .dir-locals.el
>
> Using 'package' as a field in define-configuration results in
> inconsistent indentation:
>
> --8<---------------cut here---------------start------------->8---
> (define-configuration/no-serialization mympd-configuration
> (package
> (file-like mympd) ;;;; <<<<<<<<<<<<<<<<<<<<< notice how it's indented with 2 spaces
> "The package object of the myMPD server."
> empty-serializer)
>
> (shepherd-requirement
> (list-of-symbol '()) ;;;; <<<<<<<<<<<<<<<<<<<<< vs 1 space
> "This is a list of symbols naming Shepherd services that this service
> will depend on."
> empty-serializer)
>
> ;; ...
> )
> --8<---------------cut here---------------end--------------->8---
What do you mean by inconsistent? Do you think that
’sheperd-requirement’ should be management by .dir-locals.el?
Well, .dirl-locals.el does not consider the context, IIUC.
For instance,
(let ((package something))
(package
()
)
)
Because of .dir-locals.el, the rules looks like that:
(not-in-dir-locals.el
()
)
(package
()
)
(package/inherit
()
()
)
(add-before
()
()
()
)
(let-keywords
()
()
()
()
)
Or you can see that differently,
(not-in-dir-locals.el ()
()
)
(package ()
()
)
(package/inherit ()
()
)
(add-before () ()
()
)
Well, since ’sheperd-requirement’ is not in .dir-locals.el, the
indentation seems expected. What do you consider as a bug?
Cheer,
simon
next prev parent reply other threads:[~2023-03-07 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 12:48 bug#62000: Inconsistent indentation rules for define-configuration Bruno Victal
2023-03-07 13:16 ` Simon Tournier [this message]
2023-03-07 13:54 ` Bruno Victal
2023-03-07 14:02 ` Simon Tournier
2023-06-22 13:40 ` Bruno Victal
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=86ilfcbt12.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=62000@debbugs.gnu.org \
--cc=mirai@makinata.eu \
/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.