malxau
commented
2 months ago Yori does not modify any registry key or system setting without being explicitly instructed to. It doesn’t create an Uninstaller without being instructed to (since that requires registry keys, etc.)
What sounds likely to have happened is Yori was added to the path in the installer, which is disabled by default. If that directory is deleted directly, there’s nothing I can do – it was added to system configuration by request and no Yori code was invoked to clean it up.
As I see it, the options are to use the uninstaller to remove these, or not enable these changes during the installer to begin with.
(I promise, myself and most of the people here are old sysadmin types who really don’t want software changing system state lightly. Yedit.exe can be copied around without any installer; the only reason it’s distributed in Yori is to provide an update mechanism, that it doesn’t internally include.)
I had a need to edit some things and found yori edit, I decided to give it a try because it had what I needed, unlucky me, I struggled when uninstalling, it left so many things behind, currently I don't remember exactly what, but I think it was, env variables, or registry entries, I believed it was only needed to zap the directory where it was stored and I was ok, but it was not the case, is it still like that?
I want to use yori instead of cmder for a small number of reasons, but wont do it if I have to deal with the uninstall pain again.