From: Oleg Pykhalov <go.wigust@gmail.com>
To: Pierre Neidhardt <ambrevar@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 04:59:58 +0300 [thread overview]
Message-ID: <87vaa5f0pt.fsf@gmail.com> (raw)
In-Reply-To: <87bmbxc1yc.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 26 Jun 2018 11:49:15 +0200")
[-- Attachment #1: Type: text/plain, Size: 1609 bytes --]
Hello Pierre,
Pierre Neidhardt <ambrevar@gmail.com> writes:
> Indeed! Since our discussion, Mike worked on a new implementation from scratch
> (yes, a 3rd version) which supported IPC
I don't see any major or minor versions changes of emacs-emms package
from our previous discussion. It's 5.0 still. So our previous
discussion should still be relevant. Do I miss something?
> , was backward compatible and which
> implementation was much simpler than the not-so-simple emms-player-simple-mpv.
That's why I've told you about 1936 lines in emms-player-simple-mpv
package. :-) Emms MPV implementation has only about 200 lines.
> I don't know about JSON. Can you tell me which feature you are
> looking for?
[…]
I want Emacs Emms to handle a single process as ‘emms-player-simple-mpv’
does but ‘emacs-emms’ 5.0 doesn't. I tried ‘emacs-emms’ with following
configuration, but I didn't succeeded to get a single process:
(require 'emms-setup)
(emms-all)
(emms-default-players)
Selecting next or previous item in a playlist will kill and spawn a new
‘mpv’ process.
> If there is something we should work on with the mpv player, we can discuss this
> further on the Emms mailing list.
I don't think I want to discuss anything further currently on the Emms
mailing list, because Emms mailing list is not responsible for
emacs-emms-player-simple-mpv package in Guix.
Do you have anything to prevent a revert of the change until emacs-emms
5.x will provide single process handling via JSON or another RPC?
Regards,
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-27 2:01 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 [this message]
2018-06-27 9:23 ` Pierre Neidhardt
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
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=87vaa5f0pt.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 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).