See microsoft/vscode-js-debug#990 (comment)

I think the best way for this would be for VS Code core to rename the terminal if gets a new runInTerminal request with a different name -- opened an issue for that microsoft/vscode#123189. Or, at least, try to use a terminal of the same name if one exists (which would be easier and pr

The annotation function of vue file synchronizes vscode to parse annotations of js/ts files

At present, vetur's support for vue file comments is not friendly, I hope this function can be optimized

https://user-images.githubusercontent.com/18715564/112264123-6105d300-8cab-11eb-8d9d-62604bf4b54e.mp4

https://user-images.githubusercontent.com/18715564/112264150-682ce100-8cab-11eb-9373-10

Add a topic about how the extension works on Remote Development scenarios, the default/defined approach and alternative ways, like installing on remotes and shared configs

Most of the time when I'm using this extension I am using it to mark points of interest during research. A task that I've had to perform lately is looking for hard coded text in various applications that needs to be moved to our CMS. This extension works great for that with one exception:

Generally after I have performed my research I need to document it. Using this extension I need to go to ea

Setting peacock.color or peacock.remoteColor in the user settings.json can be done manually. If set, peacock will use that color as the default color to colorize VS Code.

This should be documented in the readme, along with considerations.

Considerations:

• this can only be set or unset manually.
• this will make every vs code instance that doesnt have a color in their workspace use t