From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org, Blake Shaw <blake@nonconstructivism.com>
Subject: Re: packages won't pass white space linting -- what am I doing wrong?
Date: Fri, 12 Nov 2021 06:52:09 -0500 [thread overview]
Message-ID: <061382D5-5700-4111-BDA2-A8C68C7DCA98@lepiller.eu> (raw)
In-Reply-To: <877dddua9y.fsf@nonconstructivism.com>
Hi, it looks like the linter is correct: there is a tab at the beginning of the lines 31, 32 and following. We don't use tabs for identation, please replace them with spaces as suggested by the linter :)
Le 12 novembre 2021 02:02:17 GMT-05:00, Blake Shaw <blake@nonconstructivism.com> a écrit :
>
>hiya guix,
>
>I have a set of packages ready to send upstream, but I can't seem to
>to get them to pass tabulation tests in the linter. as an example, I
>here is the package notcurses which builds and installs fine, yet while
>I wrote it using `guix-devel-mode` in emacs and its thus indented
>accordingly, when I lint it I get:
>
>```bash
>error: TODO:: unbound variable
>hint: Did you forget a `use-modules' form?
>
>~/src/rml/unguix/notcurses.scm:31:0: notcurses@2.4.9: tabulation on line 31, column 0
>~/src/rml/unguix/notcurses.scm:32:0: notcurses@2.4.9: tabulation on line 32, column 0
>[...] ;;and so on for each line until the end of the file.
>```
>the package definition is available here:
>https://git.sr.ht/~cybersyn/rml/tree/devel/item/unguix/notcurses.scm
>
>while it appears to look like other package definitions, I can't seem to
>figure out what the issue is. I tried disabling lispy-mode, a paredit
>like emacs mode, re-tabulating and linting again, but it produce the
>same result.
>
>could this perhaps be a bug in the linter?
>
>best,
>blake
>
>--
>“In girum imus nocte et consumimur igni”
>
next prev parent reply other threads:[~2021-11-12 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 7:02 packages won't pass white space linting -- what am I doing wrong? Blake Shaw
2021-11-12 11:52 ` Julien Lepiller [this message]
2021-11-12 12:20 ` Daniel Meißner
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=061382D5-5700-4111-BDA2-A8C68C7DCA98@lepiller.eu \
--to=julien@lepiller.eu \
--cc=blake@nonconstructivism.com \
--cc=help-guix@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.
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).