unwanted - key dev PC VSC 1.58.2 has flipped into Insiders mode
See original GitHub issueIssue Type: Bug
My key dev VSC 1.58.2 has flipped into Insiders mode, as the Jupyter notebook Markdown Theme is solid grey (not very workable) and suddenly has the new cell timers. But big problem is this is buggy - the Variables (in both Jupyter and normal .py) don’t show in window (Problems and Terminal etc aok), which is critical.
Oddly, my other laptop also has exact latest 1.58.2 and does maintain the Jupyter Markdown Theme without the timers, so is normal. So, why has my core dev machine switched to what looks like Insiders release? Am trying to recommend VSC but I need a stable IDE to get my work done.
VS Code version: Code 1.58.2 (c3f126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z) OS version: Windows_NT x64 10.0.19043 Restricted Mode: No
System Info
Item | Value |
---|---|
CPUs | Intel® Core™ i7-6700 CPU @ 3.40GHz (8 x 3408) |
GPU Status | 2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled skia_renderer: enabled_on video_decode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled |
Load (avg) | undefined |
Memory (System) | 31.89GB (16.72GB free) |
Process Argv | –crash-reporter-id d2176d00-8911-4b68-94f8-b8a8636608a0 |
Screen Reader | no |
VM | 0% |
Extensions (4)
Extension | Author (truncated) | Version |
---|---|---|
python | ms- | 2021.7.1060902895 |
vscode-pylance | ms- | 2021.7.5 |
jupyter | ms- | 2021.8.1054968649 |
synthwave-vscode | Rob | 0.1.8 |
(4 theme extensions excluded)
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspyt653:30270858
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30311712
vspre833:30321513
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
vsccppwt:30329788
pythonvssor306cf:30341832
bridge0708:30335490
Issue Analytics
- State:
- Created 2 years ago
- Comments:10 (5 by maintainers)
Top GitHub Comments
From the screenshot above, it looks like you have your cursor inside the cell, which means the cell is in edit mode:
For Ctrl+K Ctrl+C to work, you’ll want to put the cell in command mode using the
Escape
key (no cursor and no blue border around the cell editor area):Hopefully that works for you 🤞
The shortcut works when the cell is in command mode. (When editing a cell, press esc to put it into command mode.) I’m on Windows and it definitely works for me (and verified Cmd+K Cmd+C also works on Mac).
VS Code notebooks support multiselecting notebook cells, but unfortunately it looks like Collapse Cell Input doesn’t handle all of them. I don’t believe we support collapsing all cell inputs today, so I’ve gone ahead and opened https://github.com/microsoft/vscode/issues/129488
Out of curiosity, is collapsing/expanding all code cells something that you frequently have to do? What is the use case for this gesture, and why would you want it surfaced in the top-level toolbar (versus, say, just in the command palette)? For context, we have received some user feedback that the new UI is visually cluttered. We’re concerned about creating additional clutter by contributing too many actions to the global toolbar, so it would help us understand the reasoning behind wanting gestures to be available in the toolbar versus somewhere else.