From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: jgart <jgart@dismail.de>, 53772@debbugs.gnu.org
Subject: [bug#53772] [PATCH] gnu: Add emacs-blacken.
Date: Fri, 04 Feb 2022 09:33:33 +0100 [thread overview]
Message-ID: <28491a2865d9d2a700a37ae315bdfed597931a72.camel@ist.tugraz.at> (raw)
In-Reply-To: <20220204065153.14445-1-jgart@dismail.de>
Am Freitag, dem 04.02.2022 um 01:51 -0500 schrieb jgart:
> * gnu/packages/emacs-xyz.scm (emacs-blacken): New variable.
> ---
> gnu/packages/emacs-xyz.scm | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
> index 521d003a6b..4d6e18f8ba 100644
> --- a/gnu/packages/emacs-xyz.scm
> +++ b/gnu/packages/emacs-xyz.scm
> @@ -29822,6 +29822,30 @@ (define-public emacs-multitran
> to the @url{https://multitran.com} online dictionary.")
> (license license:gpl3+)))
>
> +(define-public emacs-blacken
> + (package
> + (name "emacs-blacken")
> + (version "0.2.0")
> + (source
> + (origin
> + (method git-fetch)
> + (uri
> + (git-reference
> + (url "https://github.com/pythonic-emacs/blacken")
> + (commit (string-append "v" version))))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32
> "0pf9yllx0h78m925sdrg6hbv54ky2pi7cpkdsnx891qjsahvjnpy"))))
> + (build-system emacs-build-system)
> + (inputs
> + (list python-black))
> + (home-page "https://github.com/pythonic-emacs/blacken")
> + (synopsis "Python Black for Emacs")
> + (description
> +"Use the @command{python} @command{black} package to reformat
> +@command{python} buffers.")
> + (license license:gpl3)))
> +
> (define-public emacs-kibit-helper
> (package
> (name "emacs-kibit-helper")
As with all command-line utility wrappers, take care to make it
actually refer to the store path of said utility and don't just assume
it exists because it does at build time.
In your case
(emacs-substitute-variables "blacken.el"
("blacken-executable" (search-input-file inputs "/bin/blacken")))
ought to do the drill, but be warned that this is me writing untested
Scheme from memory.
Cheers
next prev parent reply other threads:[~2022-02-04 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 6:51 [bug#53772] [PATCH] gnu: Add emacs-blacken jgart via Guix-patches via
2022-02-04 8:33 ` Liliana Marie Prikler [this message]
2022-02-04 9:06 ` [bug#53772] [PATCH v2] " jgart via Guix-patches via
2022-02-04 19:51 ` bug#53772: " Liliana Marie Prikler
2022-02-04 20:36 ` [bug#53772] " jgart via Guix-patches via
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=28491a2865d9d2a700a37ae315bdfed597931a72.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=53772@debbugs.gnu.org \
--cc=jgart@dismail.de \
/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.