From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: 59000@debbugs.gnu.org
Cc: jgart <jgart@dismail.de>, 59000-done@debbugs.gnu.org
Subject: [bug#59000] [PATCH v2 1/2] gnu: Add emacs-mpv.
Date: Sun, 06 Nov 2022 15:13:17 +0100 [thread overview]
Message-ID: <875yfsmarm.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <20221103181459.15225-1-jgart@dismail.de> (jgart via Guix-patches via's message of "Thu, 3 Nov 2022 13:14:59 -0500")
Hello,
jgart via Guix-patches via <guix-patches@gnu.org> writes:
> * gnu/packages/emacs-xyz.scm (emacs-mpv): New variable.
Thank you. Applied, with the following changes.
> + (package
> + (name "emacs-mpv")
> + (version (git-version "0.0.0" revision commit))
Base version is actually 0.2.0.
> + #~(modify-phases %standard-phases
> + (add-after 'set-mpv-el-version 'patch-exec-paths
> + (lambda* (#:key inputs #:allow-other-keys)
> + (make-file-writable "mpv.el")
`make-file-writable' is not necessary.
> + (emacs-substitute-variables "mpv.el"
> + ("mpv-executable"
> + (search-input-file inputs "/bin/mpv"))))))))
> + (synopsis "Control mpv for easy note taking")
> + (description
> +"This package is a potpourri of helper functions to control a @code{mpv}
> +process via its IPC interface.")
mpv -> MPV
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2022-11-06 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:08 [bug#59000] [PATCH 1/2] gnu: Add emacs-waveform jgart via Guix-patches via
2022-11-03 18:09 ` [bug#59000] [PATCH 1/2] gnu: Add emacs-mpv jgart via Guix-patches via
2022-11-03 18:09 ` [bug#59000] [PATCH 2/2] gnu: Add emacs-waveform jgart via Guix-patches via
2022-11-03 18:14 ` [bug#59000] [PATCH v2 1/2] gnu: Add emacs-mpv jgart via Guix-patches via
2022-11-03 18:15 ` [bug#59000] [PATCH v2 2/2] gnu: Add emacs-waveform jgart via Guix-patches via
2022-11-06 14:13 ` Nicolas Goaziou [this message]
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=875yfsmarm.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=59000-done@debbugs.gnu.org \
--cc=59000@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 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).