Issue id
int64 13.1k
221k
| existing_duplicates
listlengths 1
16
| Summary
stringclasses 563
values | Created
stringclasses 563
values | Resolved
stringclasses 524
values | Description
stringclasses 563
values | Resolution
stringclasses 4
values |
|---|---|---|---|---|---|---|
221,270
|
[
219893
] |
nan
|
nan
|
nan
|
nan
|
nan
|
32,840
|
[
107433
] |
nan
|
nan
|
nan
|
nan
|
nan
|
41,574
|
[
127025
] |
Can we get a few more pixels for clicking the cursor at the beginning of a line?
|
2018-01-13 16:43:00+00:00
|
nan
|
Hello!
I'm routinely frustrated when trying to click on the beginning of a line of text to place the cursor or start a selection - I aim for it but it is very narrow (first half of the first character) and I miss and either hit the code-folding vertical or I get text-column two instead. Can that be made a little wider please?
Thanks!
*Addition by @hediet*: See #127025 for how the cursor is misleading.
|
nan
|
43,928
|
[
179238
] |
The bgcolor of selected text in highlighted search keyword is not different from the highlight color
|
2018-02-18 12:43:46+00:00
|
nan
|
### Issue Type
Bug
### Description
Steps to reproduce:
1. search some keyword in the left search panel
2. click on one search result
3. the keyword is highlighted
4. select some word in the highlighted text
I want the bgcolor of selected text differ from highlighted color, but it is the same.
(in this pic, "COUNT" is selected)
Note that this issue only occur when I open the file from search panel, and only occur on the highlight of search result I clicked.
(the second highlight works fine)
I tried 4 color themes, all reproduced this issue.
### VS Code Info
VS Code version: Code 1.20.1 (f88bbf9137d24d36d968ea6b2911786bfe103002, 2018-02-13T15:34:36.336Z)
OS version: Windows_NT x64 6.1.7601
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz (4 x 3292)|
|Memory (System)|7.96GB (3.77GB free)|
|Process Argv|C:\Program Files\Microsoft VS Code\Code.exe F:\Works\ygopro-scripts|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (1)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|1.4.5
</details>
Reproduces without extensions
|
reopened
|
69,665
|
[
119554,
117781
] |
Terminal shows corrupt texture sometimes when resuming the OS from a sleep state
|
2019-03-01 18:55:06+00:00
|
2022-12-12 15:44:18+00:00
|
**Workaround:** Press ctrl++ and ctrl+- (mac: cmd++, cmd+-) to zoom VS Code in and out which will do a complete redraw of the terminal.
---
Repro:
1. Open a terminal, run some commands
2. Sleep system
3. Resume the system (I think the delay between 2 and 3 has to be a while)
What happens exactly differs across machines, I've seen full black, full transparent and things like this:
<img width="228" alt="screen shot 2019-03-01 at 10 54 08 am" src="https://user-images.githubusercontent.com/2193314/53659411-5b467c00-3c10-11e9-9185-a63b426ce26f.png">
It seems like both the main terminal canvas texture as well as the texture atlas textures can become corrupted.
|
completed
|
73,879
|
[
111679,
121892,
121560
] |
nan
|
nan
|
nan
|
nan
|
nan
|
74,620
|
[
107971
] |
nan
|
nan
|
nan
|
nan
|
nan
|
75,141
|
[
168305,
169773
] |
"Terminal: Clear" not working as desired
|
2019-06-08 16:23:34+00:00
|
2023-12-07 17:07:25+00:00
|
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
Steps to Reproduce:
1. Run a python file using command palette >Python: Run file in terminal window
2. Terminal shows the output. Now, clear the terminal using command palette >Terminal: Clear
3. Terminal gets clear now. Run the file again in the terminal >Python: Run file in terminal window
4. Here is where issue shows up - the terminal still shows all the previous outputs from before the last clear command. IMO, desired should be that terminal should not show any previously cleared outputs.
5. Attached below is a gif of the screen reproducing & visualizing this issue
<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?:
Yes, the issue reoccurs. (Note: All except the "Python" extension were disabled. Python extension is needed to run the python file in terminal.
I had also posted in Super User forum thinking this was some issue with my system. And then I tried it on a clean build of VS code and it got repeated. Hence, I decided to post it as a bug.
[Link to Super User forum question](https://superuser.com/questions/1446320/vs-code-terminal-clear-command-not-working-as-desired)
VS Code version: Code - Insiders 1.36.0-insider (c089daa858f34631f5f827ff8a0313bf1e2ded6d, 2019-06-07T05:19:15.188Z)
OS version: Windows_NT x64 10.0.18362
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 3696)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>oop_rasterization: disabled_off<br>protected_video_decode: enabled<br>rasterization: enabled<br>skia_deferred_display_list: disabled_off<br>skia_renderer: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.68GB (7.71GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (1)</summary>
Extension|Author (truncated)|Version
---|---|---
python|ms-|2019.5.18875
|
completed
|
78,751
|
[
109895
] |
Dragging and dropping a file into a WSL terminal will use the incorrect '\' separator
|
2019-08-09 03:23:29+00:00
|
2022-12-29 20:39:48+00:00
|
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.37.0
- OS Version: 10.0.18632
Steps to Reproduce:
Drag a file to the WSL Shell
File path separator is '\\' not '/'
<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
（But in fact I have to enable Remote WSL extensions
|
completed
|
81,231
|
[
115560
] |
Remote terminals don't resolve variables when restored on startup
|
2019-09-20 13:57:27+00:00
|
nan
|
Issue Type: <b>Bug</b>
I changed my Terminal->Integrated: Cwd setting to "$(workspaceFolder)". Now, when Code starts up, the Terminal does not open, and I get a notification: "The terminal shell CWD "/home/gpudb/gpudb-dev-7.0/gpudb-core/gaiadb-cluster/${workspaceFolder}" does not exist". This happens every time I launch Code.
However, once Code has loaded, I can then do Ctrl-` to open a Terminal window, and it works as expected (also every time). Note that this is doing Remote development (so the Terminal is opening a session on my remote machine).
I suspect the issue is that Code is trying to start the Terminal before $workspaceFolder is set, but it is set later, when I manually open the Terminal. It is a fairly easy work-around, but am reporting it in case this is not the expected behavior.
VS Code version: Code 1.38.1 (b37e54c98e1a74ba89e03073e5a3761284e3ffb0, 2019-09-11T13:35:15.005Z)
OS version: Windows_NT x64 10.0.18362
Remote OS version: Linux x64 4.15.0-62-generic
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: disabled_software<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_deferred_display_list: disabled_off<br>skia_renderer: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.76GB (7.51GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|SSH: andy-linux|
|OS|Linux x64 4.15.0-62-generic|
|CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 900)|
|Memory (System)|62.86GB (6.62GB free)|
|VM|0%|
</details><details><summary>Extensions (20)</summary>
Extension|Author (truncated)|Version
---|---|---
vscode-cudacpp|kri|0.1.1
remote-containers|ms-|0.74.0
remote-ssh|ms-|0.46.1
remote-ssh-edit|ms-|0.46.1
remote-ssh-explorer|ms-|0.46.1
remote-wsl|ms-|0.39.5
vscode-remote-extensionpack|ms-|0.17.0
vs-keybindings|ms-|0.2.0
code-gnu-global|aus|0.2.2
githistory|don|0.4.6
mssql|ms-|1.6.0
cpptools|ms-|0.25.1
java|red|0.49.0
vscodeintellicode|Vis|1.1.9
vscode-java-debug|vsc|0.21.0
vscode-java-dependency|vsc|0.5.1
vscode-java-pack|vsc|0.8.0
vscode-java-test|vsc|0.19.0
vscode-maven|vsc|0.19.0
gitblame|wad|3.0.1
</details>
<!-- generated by issue reporter -->
|
nan
|
82,415
|
[
171411
] |
nan
|
nan
|
nan
|
nan
|
nan
|
82,791
|
[
167604
] |
Uninstalling language pack for current display language does not update display language setting
|
2019-10-17 17:55:47+00:00
|
2023-01-24 01:23:17+00:00
|
This is similar to https://github.com/microsoft/vscode/issues/79741 , but this is not a feature request. It's a bug. The language used in the UI becomes an inconsistent mix of 2 languages, and the current language setting remains set to something no longer valid and no longer available to the user.
Steps to repro:
1. Install a language pack.
2. Use 'Configure Display Language' command to set current display language to that language
3. Restart VS Code, as prompted
4. Uninstall the language pack
5. Restart VS Code
Seeing: VS Code has mostly fallen back to the default language, however there are still various strings in the other language. Extensions that use vscode-nls still display strings in the other language. (For example, all strings coming from the C/C++ Extension such as IntelliSense, are in the removed language. This appears to be true for some built-in VS Code extensions as well.).
Expected: When uninstalling the language pack for the currently selected display language, the setting should be reverted to the default language. Extensions that use vscode-nls should not still display the removed language. Note that the available languages in Configure Display Language only include languages there are language packs for, so it doesn't make sense for the current language setting to remain something not on that list.
Version: 1.39.2 (user setup)
Commit: 6ab598523be7a800d7f3eb4d92d7ab9a66069390
Date: 2019-10-15T15:35:18.241Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT x64 10.0.18362
|
completed
|
83,496
|
[
107523
] |
terminal.integrataed.splitCwd inherited doesn't work correctly for unicode characters
|
2019-10-29 05:01:04+00:00
|
2022-08-08 20:55:54+00:00
|
when split terminal in chinese path,error!
|
completed
|
85,930
|
[
135949
] |
nan
|
nan
|
nan
|
nan
|
nan
|
86,332
|
[
119959
] |
Markdown word not highlighting when using underscore to mark italic
|
2019-12-04 23:13:22+00:00
|
2022-12-05 21:47:07+00:00
|
Issue Type: <b>Bug</b>
**Repo**
1. For the md:
```
_it_
*it*
```
1. Put cursor on `it` on first line
**Expected**
Both `it`s get highlighted
**Actual**
Only second `it` gets highlighted
VS Code version: Code - Insiders 1.41.0-insider (7f1975a4fb29d0a788c21f17eb2aad056fec22d8, 2019-12-04T10:18:55.163Z)
OS version: Darwin x64 18.7.0
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off<br>surface_control: disabled_off<br>surface_synchronization: enabled_on<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (1.01GB free)|
|Process Argv||
|Screen Reader|no|
|VM|22%|
</details>
<!-- generated by issue reporter -->
|
not_planned
|
86,964
|
[
135113
] |
Allow files deleted in VS Code to be "put back" on macOS
|
2019-12-13 23:26:38+00:00
|
2022-12-12 16:12:32+00:00
|
Right now if you delete a file (eg. using <kbd>Right-click</kbd><kbd>Delete</kbd>) and then go to that file in the trash, there is no <kbd>Put Back</kbd> option.
Whereas if you delete a file anywhere else in macOS (eg. using <kbd>Right-click</kbd><kbd>Move to Trash</kbd>) and then find it in the trash, you'll be able to select <kbd>Put Back</kbd> and have it return to where it was. This is helpful when you accidentally delete something and want to restore it.
Is it possible for VS Code to support this?
|
not_planned
|
93,001
|
[
198582,
205471
] |
resolving multiple tasks with type npm and same script fails
|
2020-03-19 10:44:00+00:00
|
nan
|
Issue Type: <b>Bug</b>
Create 2 tasks with "type": "npm" and same "script"
Expected both tasks to be resolved by their label
- VsCode will list only one of those tasks when listing available tasks with "Tasks: Run Task".
- Depending tasks will fail with "Couldn't resolve dependent task 'x' in workspace folder 'y'" in the "Tasks" output.
**tasks.json:**
```json
{
"version": "2.0.0",
"tasks": [
{
"label": "start_both",
"type": "shell",
"dependsOn": [
"start_nr_1",
"start_nr_2"
],
"problemMatcher": []
},
{
"label": "start_nr_1",
"type": "npm",
"script": "start",
"problemMatcher": []
},
{
"label": "start_nr_2",
"type": "npm",
"script": "start",
"options": {
"env": {
"SOME": "option"
}
},
"problemMatcher": []
},
]
}
```
**package.json:**
```json
{
"scripts": {
"start": "echo running 'start' script"
}
}
```
VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:01:20.184Z)
OS version: Windows_NT x64 10.0.19041
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 x 3592)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.92GB (8.47GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
|
nan
|
94,708
|
[
112589
] |
nan
|
nan
|
nan
|
nan
|
nan
|
95,021
|
[
111930
] |
Task terminal truncates long/quick output.
|
2020-04-11 20:14:04+00:00
|
nan
|
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- Use Help > Report Issue to prefill these. -->
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:44:52.965Z)
OS version: Linux x64 5.4.25
### Steps to Reproduce
Run "test" task using this `.vscode/tasks.json`:
```json
{
"version": "2.0.0",
"tasks": [
{
"label": "test",
"type": "shell",
"command": "seq 1000 | sed 's/$/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/'",
}
]
}
```
### Expected behavior
All 1000 lines are printed, the last 3 lines being:
(this is how it works when ran in a regular VSCode Terminal)
```
998XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
999XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1000XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
```
### Actual behavior
Task output is truncated randomly, these being two example runs' last 3 lines:
```
741XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
742XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
743XXXXXXXXXXXXXXXXX
```
```
754XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
755XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
756XXXXXXXXXXXXXXX
```
### Additional background
Reading the description of #75139, I'm *pretty sure* it's the same bug.
It was marked as a duplicate of #38137, but I'm not sure that's correct.
I've only seen this in the last few months, *after* #38137 was supposedly fixed, and assumed the problem was a change in the process producing the output, or some bug/setting in SSH, which is why I haven't reported it earlier.
However, after coming across #75139, I did some experimentation, and even a task that only does `cat build-log` results in truncation (`build-log` is 128kB and has 2665 lines, the current output from a real workload).
And then I simplified that to the command above, which reproduces easily.
Even `seq 1000` alone was truncated once, at `841`.
And `seq 10000` truncates even easier, example last 3 lines from some runs:
```
9595
9596
959
```
```
7437
7438
7439
```
```
8143
8144
814
```
|
nan
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.