VS Code Can Do That - Workshop
1.0.0
1.0.0
  • Introduction
  • Essential Keyboard Shortcuts
  • Exercise 1 - Customizing The Editor
    • Before you start
    • Switch themes
    • Install a new icon theme
    • Switch fonts
    • Editor tweaks
    • Change default Settings view
    • Easily identify editor instances
  • Exercise 2 - Productivity Tricks
    • Before you start
    • Essential navigation shortcuts
    • Creating HTML with Emmet
    • Styling with Emmet
    • Update image sizes
  • Exercise 3 - Navigation And Refactoring
    • Before you start
    • Moving, Duplicating and Deleting
    • Folding sections
    • Multiple cursors
    • Rename refactor
    • Finding things
    • Extract refactor
  • Exercise 4 - Debugging
    • Before you start
    • Simple debugging
    • Simple launch config
    • Auto attach
    • Debugging browser apps
    • Compound debug configurations
  • Exercise 5 - Docker
    • Untitled
Powered by GitBook
On this page

Was this helpful?

  1. Exercise 1 - Customizing The Editor

Easily identify editor instances

PreviousChange default Settings viewNextBefore you start

Last updated 5 years ago

Was this helpful?

There is a popular extension called "Peacock". It is useful for identifying editor instances when you have multiples of them open. This extension is included in the VS Code Can Do That extension pack.

  • Open the Command Palette (Cmd/Ctrl + Shift + P)

  • Select "Peacock: Enter a color"

  • Enter in any color

I find that it's most useful to set just the titlebar color with Peacock. This is enough to let me know at a quick glance which editor instance I'm looking at. For that reason, I disable the "Status Bar" and "Action Bar" theming in Peacock.

  • Open Settings (Cmd/Ctrl + ,)

  • Add in the following two lines...

    • "peacock.affectActivityBar": false

    • "peacock.affectStatusBar": false