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
Gitlens sets activeFileStatus as a reaction to the user changing the active text editor.
This causes flickering of the editor toolbar, as git lens registers commands that use a specific value of activeFileStatus as precondition and this context key is updated asynchronously:
Instead of gitlens:activeFileStatus: tracked|blameable|remotes|, I suggest to have various arrays:
You can still lazily update these arrays depending on the active editor, but then at least it only flickers once (when current editor uri is initially added to the array) and not on every switch.
GitLens Version
latest
VS Code Version
latest
Git Version
latest
Logs, Screenshots, Screen Captures, etc
No response
The text was updated successfully, but these errors were encountered:
Description
Gitlens sets
activeFileStatus
as a reaction to the user changing the active text editor.This causes flickering of the editor toolbar, as git lens registers commands that use a specific value of
activeFileStatus
as precondition and this context key is updated asynchronously:Instead of
gitlens:activeFileStatus: tracked|blameable|remotes|
, I suggest to have various arrays:gitlens:trackedFiles: [...]
gitlens:blameableFiles: [...]
gitlens:remotesFiles: [...]
Then, you can use the
in
operator.You can still lazily update these arrays depending on the active editor, but then at least it only flickers once (when current editor uri is initially added to the array) and not on every switch.
GitLens Version
latest
VS Code Version
latest
Git Version
latest
Logs, Screenshots, Screen Captures, etc
No response
The text was updated successfully, but these errors were encountered: