Highlight tabs whose file has problems, is untracked or modified compared to repo version

[mcaquet]

Could you please provide a highlighting colors setting for tabs whose file is modified compared to repo version, or became untracked after a file renaming ?

I know there is a little U or M appearing on the right of file names when file is Untracked or Modified:

This is not highlighting these tabs enough imo. Also, if VSCode identifies problems in the file, the problem count is displayed next to the M letter, but the file name's font color changes from orange to default color.

The orange or custom color should stay, even if a problem is identified in the file.

Ability to have a different color for staged and unstaged changed files, and untracked files would be ideal, especially after a file renaming.

Thanks in advance Mathias

[benibenj]

This is the setting you are looking for: workbench.editor.highlightModifiedTabs

[mcaquet]

This is the setting you are looking for: workbench.editor.highlightModifiedTabs

I already have this setting to true @benibenj My request is not to highlight files that are "dirty" i.e. modified but not saved. My request is to highlight files that have been modified compared to the repository version, which means they would stay highlighted until I commit them into the git repository. Reposting the request.

[vs-code-engineering[bot]]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[mcaquet]

I noticed that if VSCode identifies a problem in the file, the problem count is displayed next to the M letter in the tab, but the file name's font color changes from orange to default color. This seems like a bug to me, font color should stay different when the file is modified, possibly in a different color if a problem is detected, but surely not reverting to default color. Should I create a new issue for this "bug" @benibenj ?

[benibenj]

Yes, ideally with a video/gif/images to help explain

[mcaquet]

Yes, ideally with a video/gif/images to help explain

I did: https://github.com/microsoft/vscode/issues/238040

[vs-code-engineering[bot]]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[vs-code-engineering[bot]]

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.

Happy Coding!