@chrisaww as a Geany developer I build Geany/Plugins from Git, I don't install from distros, so I know what is/is not built and installed on my system, and Markdown Plugin is not built because I have not installed its build dependencies because I don't use markdown.

Plugins can have inter-dependencies and, if another plugin depends on it, a plugin is no longer removable until the other plugin is closed. That is not the case with markdown, but maybe markdown or another plugin is confusing something when it registers with Geany.

Since there are no other reports of markdown being permanently enabled I suspect it probably is just you, hence my concern you were mixing packages. Try running Geany without any configuration geany -c /tmp/does_not_exist and see if it is still enabled.

As I said above, plugins are created and maintained by individuals, not the Geany team (even team members are acting as individuals if they happen to maintain a plugin), so probably best to report it on geany-plugins where the markdown plugin is maintained.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.