Re: integration with beets

Yoni Rabkin <[email protected]> writes:

> Aleksas Tunikas <[email protected]> writes:
>
>> I want to make the beets plugin 'play' to redirect the output 
>> to emms,
>> by default it already do that, so I must have beed specifying 
>> it
>> somewhere in my system, but it starts a new Emacs instance 
>> every time,
>> what I want instead is that it utilize emacsclient, the 
>> syntaxis to put
>> a custom command is like this: command: /usr/bin/command 
>> --option1
>> --option2 some_other_option (from this
>> https://beets.readthedocs.io/en/stable/plugins/play.html) 
>>
>> Or optionally maybe somebody knows where to change those 
>> default
>> settings it appears to be related to the xdg-open explained 
>> here:
>> https://wiki.archlinux.org/title/default_applications
>>
>> Meanwhile if I find the answer before somebody pointed out I 
>> will report
>> here.
>>
>> Thank you and have a great day!
>
> I saw today on IRC that you were advancing with this. Definitely 
> send in
> a recipe if you figure this out.
>
> However, it would also be good if you can list the features of 
> beets
> that you think are missing in Emms. Perhaps we can use that as a 
> way to
> help roadmap tagging and library management in Emms.
>
IMO, MPD/EMMS and beets are complimentary -- they do very 
different things, in different ways.  I think some tighter 
integration might be nice, but I don’t think all the stuff beets 
does makes sense to have in EMMS.

  — Ian