From: Oleg Pykhalov <go.wigust@gmail.com>
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 31933@debbugs.gnu.org
Subject: [bug#31933] ‘emacs-emms-next’ supports JSON RPC
Date: Wed, 27 Jun 2018 15:37:06 +0300 [thread overview]
Message-ID: <87lgb0flsd.fsf_-_@gmail.com> (raw)
In-Reply-To: <877emkvb0p.fsf@gmail.com> (Pierre Neidhardt's message of "Wed, 27 Jun 2018 11:23:02 +0200")
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
Hello Pierre,
Pierre Neidhardt <ambrevar@gmail.com> writes:
> O my, I'm so sorry, I got terribly confused with all the updates happening and
> got carried away into thinking that a new version of Emms had been released
> since 5.0! :/
No problem, :-)
> The changes I was referring to are still on master but there is no new release
> since 5.0.
Ah, now I see. Thank you for pointing on this. Seems that Yoni Rabkin
recent patch series beginning are what I'm asking for.
http://git.savannah.gnu.org/cgit/emms.git/commit/?id=55c83369162231b31433cd404466e5641cd90353
> That 3rd implementation of the mpv backend should answer all your
> needs regarding the single-process RPC.
>
> So now:
>
> - Either we upgrade Emms to current master. There is no urgent need for it as
> far as Guix is concerned.
>
> - Or we revert my patch. We can re-apply it later once a new version of Emms
> has been released.
A third option is to have emacs-emms-next package builded from a master
branch, but we have a policy to stick to release versions. I'll use the
following package recipe for myself unless somebody wants to have it in
Guix package collection, too. Fill free to take and push it.
(define-public emms-next
(let ((commit "9f9a9b81f741692f2d188d1b46e72f2b6db8a9a1"))
(package
(inherit emms)
(name (string-append (package-name emms) "-next"))
(version (git-version (package-version emms) "1" commit))
(source
(origin
(inherit (package-source emms))
(uri (string-append
"https://git.savannah.gnu.org/cgit/emms.git/snapshot/emms-"
commit ".tar.gz"))
(sha256
(base32
"1wg00dr35h9shs6782s20nds8razqibys9ipzi9aa2kb3yhkdp6q")))))))
Thanks,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-27 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 17:15 [bug#31933] [PATCH 1/2] gnu: emacs-emms-player-simple-mpv: Deprecate in favor of Emms 5.0+ Pierre Neidhardt
2018-06-21 17:19 ` [bug#31933] [PATCH 2/2] gnu: emacs-emms-player-mpv: " Pierre Neidhardt
2018-06-25 19:56 ` bug#31933: [PATCH 1/2] gnu: emacs-emms-player-simple-mpv: " Ludovic Courtès
2018-06-25 22:57 ` [bug#31933] ‘emacs-emms-player-simple-mpv’ is not ‘emms-player-mpv.el’ Oleg Pykhalov
2018-06-26 9:49 ` Pierre Neidhardt
2018-06-27 1:59 ` Oleg Pykhalov
2018-06-27 9:23 ` Pierre Neidhardt
2018-06-27 12:37 ` Oleg Pykhalov [this message]
2018-06-27 13:52 ` [bug#31933] ‘emacs-emms-next’ supports JSON RPC Pierre Neidhardt
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=87lgb0flsd.fsf_-_@gmail.com \
--to=go.wigust@gmail.com \
--cc=31933@debbugs.gnu.org \
--cc=ambrevar@gmail.com \
/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.