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
If VCS found, check the dir's "status" (i.e. git status)
Add zero-width Unicode characters to the dirmsg property of the file, based on it's tracked/untracked/ignored/etc. status
Add pattern-matching to the zero-width chars into syntax.yaml to colorize each file/dir based on status.
I'd like some input as to which of Micro's syntax types should be used for tracked/untracked/ignored/etc. so feel free to recommend them.
Having ignored files be "comments" is pretty obvious, but everything else is kind of up in the air.
Note that an onSave hook will need to be added, which will trigger a re-scan of VCS status on the file, and a change of the dirmsg, where appropriate. This will allow the colors to adjust as you work on files.
On second thought, instead of re-coloring files we could put little ascii indicators for the git status (or even combine indicator & color?). Maybe both could be made optional as well.
The text was updated successfully, but these errors were encountered:
filemanager-vcscolors
git status
)dirmsg
property of the file, based on it's tracked/untracked/ignored/etc. statussyntax.yaml
to colorize each file/dir based on status.I'd like some input as to which of Micro's syntax types should be used for tracked/untracked/ignored/etc. so feel free to recommend them.
Having ignored files be "comments" is pretty obvious, but everything else is kind of up in the air.
Note that an
onSave
hook will need to be added, which will trigger a re-scan of VCS status on the file, and a change of thedirmsg
, where appropriate. This will allow the colors to adjust as you work on files.On second thought, instead of re-coloring files we could put little ascii indicators for the git status (or even combine indicator & color?). Maybe both could be made optional as well.
The text was updated successfully, but these errors were encountered: