Josh Kunz

This seems like a great idea. Having `ashuffle` exit on all server failures was an easy choice when this was a little script, but it's probably time we properly handle...

Took a look at this. It doesn't look like EditorConfig has a lot of options, so I'm not sure how helpful it would be. That said it seems widely supported,...

That's not a bad idea. It could probably key off of the [`db_update` field of the `stats` command](https://www.musicpd.org/doc/html/protocol.html#command-stats). A big question for me, is how it would interact with filters....

Thanks for the detailed bug report. > Does ashuffle have a version number? Can't report that. ashuffle does have a version number, but it's not easily reportable from the CLI....

Thanks for the investigation! This definitely looks like a bug in libmpdclient. As I mentioned in the previous comment, there is a PR upstream to get this fixed. I filed...

I'll keep it brief since it's not really related to the issue at hand. Feel free to open a new issue to discuss new enhancements/features you'd like to see in...

High level comment for this thread: I'm pretty bummed that there hasn't been any movement on this on the `libmpdclient` side. I'd really prefer not needing weird work-arounds to solve...

> Agreed. I'm just trying to be pragmatic here as without any workarounds, ashuffle is essentially unusable (crashes on startup) because of this issue (if you're unwilling to edit your...

I took a look at `mpc listall` and it looks like they [call `mpd_send_list_all`](https://github.com/MusicPlayerDaemon/mpc/blob/master/src/command.c#L609-L612) in the case where there is no special formatting. That should work great for ashuffle, so...

> I'll merge that and cut a release tomorrow when the integration tests have run. This has been cut into v3.12.0, but I'm having some trouble with the automation. I...