I am well aware of the Unix Domain socket issue with Geany and `sudo` discussed at length in #1411 and reported by users in #294, #1411, and #1615. However, prior discussion has focused on what Geany's behavior should be when invoked with `sudo` and how users can resolve the issue.
**This situation, where a file in Geany's configuration is invalid for whatever reason, is one that Geany should more facilitate a more graceful recovery from.** Requiring the user to search the internet to discover how to fix the problem, and then having them need to manually delete a configuration file is not a satisfactory user experience. Specifically, I would suggest that the dialog [found in the code here](https://github.com/geany/geany/blob/935c16ea25374d323ec4212a1a49bdce68d4603b/src/socket.c#L224) should be modified to include an option for Geany itself to delete the problematic socket (`~/.config/geany/geany_socket_*`), including the potential consequences of this action. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2102
