You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think being able to do e.g. sopel-plugins disable thiswasremoved via the CLI would be helpful.
Problems Solved
After deleting or uninstalling a plugin called name, if one doesn't do it ahead of time, sopel-plugins disable name will display "No plugin named name." and leave the config file untouched.
Alternatives
The alternative (and current workaround) is to manually edit the .cfg file.
Notes
I'm using core.enable on my test bot, so I noticed the inability to disable a removed plugin. There's probably behavior that would be similarly useful for the core.exclude setting (from which plugins are usually removed with sopel-plugins enable, but I haven't spent the time to figure out how that should look yet. (This is already enough non-8.0.0-relevant work for one day!)
The text was updated successfully, but these errors were encountered:
Requested Feature
I think being able to do e.g.
sopel-plugins disable thiswasremoved
via the CLI would be helpful.Problems Solved
After deleting or uninstalling a plugin called
name
, if one doesn't do it ahead of time,sopel-plugins disable name
will display "No plugin named name." and leave the config file untouched.Alternatives
The alternative (and current workaround) is to manually edit the
.cfg
file.Notes
I'm using
core.enable
on my test bot, so I noticed the inability todisable
a removed plugin. There's probably behavior that would be similarly useful for thecore.exclude
setting (from which plugins are usually removed withsopel-plugins enable
, but I haven't spent the time to figure out how that should look yet. (This is already enough non-8.0.0-relevant work for one day!)The text was updated successfully, but these errors were encountered: