From: Pierre Neidhardt <ambrevar@gmail.com>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 31933@debbugs.gnu.org
Subject: [bug#31933] ‘emacs-emms-player-simple-mpv’ is not ‘emms-player-mpv.el’
Date: Wed, 27 Jun 2018 11:23:02 +0200 [thread overview]
Message-ID: <877emkvb0p.fsf@gmail.com> (raw)
In-Reply-To: <87vaa5f0pt.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
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! :/
The changes I was referring to are still on master but there is no new release
since 5.0. 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.
Sorry for the mess! :p
--
Pierre Neidhardt
Trust everybody, but cut the cards.
-- Finlay Peter Dunne, "Mr. Dooley's Philosophy"
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-06-27 9:24 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 [this message]
2018-06-27 12:37 ` [bug#31933] ‘emacs-emms-next’ supports JSON RPC Oleg Pykhalov
2018-06-27 13:52 ` 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=877emkvb0p.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=31933@debbugs.gnu.org \
--cc=go.wigust@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.