Closed ranelpadon closed 2 years ago
Hi, thanks for the issue! Yup, the plugin doesn't load blames when it's disabled, that's why you get the exception. I think what you tried to do is the expected behavior and will fix it on weekends or sooner :)
It's fixed now :)
@f-person Confirmed to be working. Thanks a lot. :)
I disabled this plugin on startup since I don't want to have clutter:
But when running
:GitBlameCopySHA
or:GitBlameOpenCommitURL
, it will trigger this error and will not work:Apparently, I need to enable the plugin first (via
:GitBlameEnable
or:GitBlameToggle
) before I could execute those 2 commands, which is not good UX I think. Ideally, the plugin should be enabled automatically when it's disabled before performing actions such as:GitBlameCopySHA
or:GitBlameOpenCommitURL
, then revert back to disabled after performing the actions.I tried this also but it didn't work (same error):
Am I missing something? Or could we have a flag/setting to have this kind of behavior? Thanks :)