From: Robert Vollmert <rob@vllmrt.net>
To: 36240@debbugs.gnu.org
Subject: bug#36240: indent-code.el is not aware of (package (inherit ...)) style
Date: Sun, 16 Jun 2019 09:07:02 +0200 [thread overview]
Message-ID: <4F2510DB-73D5-4817-804B-21F065E9DE26@vllmrt.net> (raw)
When encountering a package definition that starts
(package (inherit other-package))
etc/indent-code.el will indent the rest of the package body
to align with the start of (inherit. That seems to be a
common idiom, used in roughly half of the instances:
guix/gnu/packages$ git grep '(inherit ' | wc -l
905
guix/gnu/packages$ git grep '(inherit ' | grep package | wc -l
425
next reply other threads:[~2019-06-16 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-16 7:07 Robert Vollmert [this message]
2019-06-17 9:39 ` bug#36240: indent-code.el is not aware of (package (inherit ...)) style Ludovic Courtès
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=4F2510DB-73D5-4817-804B-21F065E9DE26@vllmrt.net \
--to=rob@vllmrt.net \
--cc=36240@debbugs.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 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).