It seems weird that we're putting a socket file in a config directory. We should probably use
g_get_user_runtime_dir()
.
Maybe, but it's mostly irrelevant to the OP's point, because either way it'd be in the same place as the user's one.
Also, while indeed it sounds like a socket is a good candidate for a runtime directory, it would make it harder for us as we -- for the moment -- still want to let the user change it (-c
), so then we'd need 2 separate flags, or different relative socket location depending on whether -c
was passed or not. IMO, we should rather not change anything here until we have a compelling reason to.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.