Discussion:
[emms-help] mpd host socket not supported
Mark Oteiza
2017-09-16 15:36:40 UTC
Permalink
Hi,

EMMS appears to not support MPD_HOST being the absolute path of a
socket. Doing emms-player-mpd-connect gives

/run/user/1000/mpd/socket/6600 Name or service not known

mpc.el in Emacs >=25 has code for handling this. I believe all the bits
can be found by searching for file-name-absolute-p
Yoni Rabkin
2017-09-18 20:24:02 UTC
Permalink
Thanks for the bug report.
Post by Mark Oteiza
Hi,
EMMS appears to not support MPD_HOST being the absolute path of a
socket. Doing emms-player-mpd-connect gives
/run/user/1000/mpd/socket/6600 Name or service not known
mpc.el in Emacs >=25 has code for handling this. I believe all the bits
can be found by searching for file-name-absolute-p
I'll look into this for the upcoming release (unless some beats me to it
with a patch of course!)
--
"Cut your own wood and it will warm you twice"
Yoni Rabkin
2017-10-08 15:34:26 UTC
Permalink
Post by Mark Oteiza
Hi,
EMMS appears to not support MPD_HOST being the absolute path of a
socket. Doing emms-player-mpd-connect gives
/run/user/1000/mpd/socket/6600 Name or service not known
I understand that this requires mpd to listen on a unix socket and not
at a particular network address (I don't use mpd)

Can you please send me the relevant bits of your mpd config so that I
can easily recreate this set up here? I'd like to spend my time hacking
Emms, not trying to understand mpd.
Post by Mark Oteiza
mpc.el in Emacs >=25 has code for handling this. I believe all the bits
can be found by searching for file-name-absolute-p
_______________________________________________
Emms-help mailing list
https://lists.gnu.org/mailman/listinfo/emms-help
--
"Cut your own wood and it will warm you twice"
Mark Oteiza
2017-10-08 16:10:47 UTC
Permalink
Post by Yoni Rabkin
Post by Mark Oteiza
Hi,
EMMS appears to not support MPD_HOST being the absolute path of a
socket. Doing emms-player-mpd-connect gives
/run/user/1000/mpd/socket/6600 Name or service not known
I understand that this requires mpd to listen on a unix socket and not
at a particular network address (I don't use mpd)
Can you please send me the relevant bits of your mpd config so that I
can easily recreate this set up here? I'd like to spend my time hacking
Emms, not trying to understand mpd.
No problem. The only config needed for this is

bind_to_address "/path/to/mpd/socket"

then invoking `mpd` should create the specified socket and run.
Yoni Rabkin
2017-10-20 20:58:24 UTC
Permalink
Post by Mark Oteiza
Post by Yoni Rabkin
Post by Mark Oteiza
Hi,
EMMS appears to not support MPD_HOST being the absolute path of a
socket. Doing emms-player-mpd-connect gives
/run/user/1000/mpd/socket/6600 Name or service not known
I understand that this requires mpd to listen on a unix socket and not
at a particular network address (I don't use mpd)
Can you please send me the relevant bits of your mpd config so that I
can easily recreate this set up here? I'd like to spend my time hacking
Emms, not trying to understand mpd.
No problem. The only config needed for this is
bind_to_address "/path/to/mpd/socket"
then invoking `mpd` should create the specified socket and run.
Sorry for taking so long to get around to this. I've pushed an
experimental patch to the git repo for you to test (works here).

Please set `emms-player-mpd-server-name' to the socket (for me it was
simply "/run/mpd/socket"), and then set `emms-player-mpd-server-port' to
nil (this is how the code knows it's a socket and not a network
connection.)
--
"Cut your own wood and it will warm you twice"
Loading...