News for hackers. Stuff that matters.

A comment on Visual Studio Code 1.8. Parent comment

Re:Visual Studio Code 1.8 by WA on Wednesday December 14, 2016 @05:09PM (#13180110)
Can't upvote this enough. One dev mentioned in a GitHub issue that the blue color is for branding reasons [1]. This is so absurd, it hurts. That status bar is the most distracting and annoying thing ever.

See link for suggestions how to mitigate. I use the tip from the person named sysrpl. VSCode is unusable with that blue color for me.

1: https://github.com/Microsoft/vscode/issues/1884

[ Parent | on HN ]
Re:Visual Studio Code 1.8 by seanmcb on Wednesday December 14, 2016 @05:37PM (#13180332)
We do have a plan to enable this - unfortunately it did not make 1.8 but we plan to work on it in 1.9. So you should have some additional options soon.

Sean - VS Code Team Member

[ Parent | on HN ]
Re:Visual Studio Code 1.8 by pitaj on Wednesday December 14, 2016 @10:42PM (#13182197)
Is it possible to add for a way for the user to have a custom CSS file? I really like how Atom provides such great visual customization by just giving the user a less file that they can edit.
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by octref on Wednesday December 14, 2016 @05:25PM (#13180246)
On the other hand, you can toggle it off by View -> Hide Status Bar.
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by lowmagnet on Wednesday December 14, 2016 @08:52PM (#13181677)
I never even noticed that it was blue as a branding thing. You can toggle it off with Super-K Z now.
[ Parent | on HN ]
Re:Visual Studio Code 1.8 by WA on Thursday December 15, 2016 @02:19AM (#13183029)
Neither did I. When I first opened VSCode, I thought it wanted to tell me about something important going on. Maybe color coded an update message or something like that.
[ Parent | on HN ]