"There are no changes to commit”

[ghost]

Frequently, even without my latest settings changes, the extension has complained that “There are no changes to commit” despite there being changes. I've thought this to be due to the sluggishness of VSCode actually writing files on disk (in 2020!). Recently, to reduce the massive CPU usage and battery drain of VSCode due to vscode-hg polling (exploding due to the VSCode refuse-to-fix issues described in #156), I set

    "hg.autoInOut": false,
    "hg.autoRefresh": false,

After this, it is impossible to commit at all from the extension. Always “There are no changes to commit”.

Update: Manually running Hg: Refresh and then Hg: Commit works. Makes me think, does autoRefresh actually induce periodical polling, or just autoInOut? I think it would make sense for Hg: Commit and other operations to refresh the internal state—before and after. But no periodical polling, please. All programs doing such things in a busyloop just kills the battery.