unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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: Tue, 26 Jun 2018 11:49:15 +0200	[thread overview]
Message-ID: <87bmbxc1yc.fsf@gmail.com> (raw)
In-Reply-To: <87r2kuo4oi.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 573 bytes --]

Indeed!  Since our discussion, Mike worked on a new implementation from scratch
(yes, a 3rd version) which supported IPC, was backward compatible and which
implementation was much simpler than the not-so-simple emms-player-simple-mpv.

I don't know about JSON.  Can you tell me which feature you are looking for?
I'll look into it.

If there is something we should work on with the mpv player, we can discuss this
further on the Emms mailing list.

Cheers!

-- 
Pierre Neidhardt

Recursion n.:
	See Recursion.
		-- Random Shack Data Processing Dictionary

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-06-26  9:50 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 [this message]
2018-06-27  1:59     ` Oleg Pykhalov
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=87bmbxc1yc.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 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).