João Pedro

I also noticed that Mopidy doesn't seem to accept comments in the same line as configuration options in the configuration file. So something like ``` [audio] mixer = software #...

> > I also noticed that Mopidy doesn't seem to accept comments in the same line as configuration options in the configuration file. > > Yes, that is #1868 Ah,...

can we make it "mandatory" that plugins install the manual pages if they are available? `~/.local/share/man` should be respected in all Unix environment, as far as i know. i love...

> Any thoughts? I dont love the use of "find" to locate the man pages, but it was very quickly apparent that there was no consistency between plugins as to...

> @WhoNeedszZz the "shortest" path to integrate this would be implementing a function like > > ``` > (defn pnp-resolve [state build-config from require] ...) > ``` > > `from`...

also, similarly to what i did in #46, i tried formatting the tests file, but i've also done it as the last commit, making it easy to revert it. there...

i have also devised a way to have functions map on response, but it could be achieved with `verb-post-response-hook`, albeit not as elegantly as with the request mapping. i could...

i have also taken the liberty to clean up and improve some functions that i ended up stumbling upon, but i could always create a new PR with those changes...

do you have any idea on how to do so? i guess submitting a PR is an easier way to get a response i really have no idea on how...

hey, just chiming in to preset to you guys the [`notmuch-indicator`](https://git.sr.ht/~protesilaos/notmuch-indicator) package from Prot. the code for the notmuch unread count is there and very neatly organized as is usual...