The Wayback Machine - https://web.archive.org/web/20200708195205/https://github.com/topics/vscode-extension
Skip to content
#

vscode-extension

Here are 2,764 public repositories matching this topic...

lannonbr
lannonbr commented Nov 24, 2018

There may be paid VS Code extensions or content that could be beneficial to list here. Currently there is no direct notice in the contributing guide that submissions should only be publicly available / free resources, so I think at least it would be good to update the guide with our stance on it.

I do think pushing free resources first should be a priority, but if there is a paid resource that

DanDPanda
DanDPanda commented Sep 13, 2019

Describe the bug
When I grab multiple lines of text in visual mode and click S, it is expected that it deletes all lines that are selected and puts me into insert mode. But what is happening instead is that it puts me into insert mode and allows me to insert one character at the start and beginning of the selection.

To Reproduce
Steps to reproduce the behavior:

  1. Open the file
vscode-gitlens
DaniGTA
DaniGTA commented Dec 23, 2019

🚀 Feature Proposal

This debug button is present when the test fails and this works nice.

Lately I've been writing a lot of tests and some of them were green although they weren't supposed to be. It would be great if the debug button was there when the test was successful.

As a workaround i just add a fail() and wait until the test fails, then i can debug it.

📷 Screenshots

The

dgomezc
dgomezc commented Oct 1, 2019

We should use docs for our documentation and wiki for additional contents and notes

Docs structure:

📁 Contributing
       📄 Accessibility.md
       📄 Architecture.md
       📄 Getting-started-developers.md
       📄 Templates.md

📁 Generated Apps
       📁 Backend-frameworks
             

sipi
sipi commented Aug 8, 2018

One bold, verbatim, italic, underline or code character followed by text then an other same highlighting does not correctly displayed.
In the snippet below, all the "should not" part are highlighted. Except for strike-through that is not managed at all.

*b* should not bold *bold* 
=v= should not verb =verb= 
_u_ should not underline _underline_
/i/ should not italic /ital
lostintangent
lostintangent commented Mar 22, 2020

Currently, tours are persisted as JSON files and written to the “.tours” directory of your repo. However, we could also explore allowing tours to be defined via actual code comments. For example, the following could represent a step definition above a line of code:

// CodeTour: <tourTitle> <stepNumber> <stepDescription>

While this approach could help mitigate tour decay,

Dart-Code
Coder-256
Coder-256 commented Jan 19, 2020

OS: macOS 10.14.6
VSCode version: 1.41.1
Extension version: 1.4.5
Python version: 3.7.6
LLDB version: 9.0.1
Rust version: 1.40.0 (stable)

There should be a warning for invalid/old breakpoints because until you manually right-click on the breakpoint list and choose "Reapply All Breakpoints" while the program is running, there is no indication that they will never fire. They should also be m

Improve this page

Add a description, image, and links to the vscode-extension topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the vscode-extension topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.