Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python docstring auto-inserts triple quotes at both cursors in a file during Live Share #127910

Closed
aely-aronoff opened this issue Jul 2, 2021 · 2 comments
Assignees

Comments

@aely-aronoff
Copy link

Issue Type: Bug

Hello, hello. Firstly, let me say I really love VS Code and Live Share and use it all the time with my team. Fantastic work!

There is a bug we've noticed and I'm not sure if it's coming from Live Share or the Python extension but here's what happens:

  • On host machine, when I type the opening triple quotes of a docstring (""") it automatically inserts the closing triple quotes, which is desired behavior.
  • When I'm on Live Share with another dev on a remote machine, if they type an opening triple quote it automatically inserts the closing triple quotes at my cursor instead of at their cursor.

This is a little annoying since any time the other dev starts a docstring I suddenly have three quotes appear wherever I'm writing code. Note that this only happens when we're both editing the same file - it doesn't happen if we're editing different files. It also doesn't happen when the other dev starts a regular string with quote (") or apostrophe ('). Only with the docstrings.

I haven't tested this on other pairs of computers, but my computer is a Windows machine and the other dev is on a MacBook Pro, MacOS v11.1.

VS Code version: Code 1.57.1 (507ce72, 2021-06-17T13:28:07.755Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

System Info
Item Value
CPUs Intel(R) Core(TM) i7-10700F CPU @ 2.90GHz (16 x 2904)
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.92GB (18.50GB free)
Process Argv --crash-reporter-id 823b39f3-cbe6-4f28-9268-d408bb416063
Screen Reader no
VM 0%
Extensions (10)
Extension Author (truncated) Version
vscode-sqlite ale 0.13.0
go gol 0.26.0
vscode-edit-csv jan 0.6.0
solidity Jua 0.0.124
python ms- 2021.6.944021595
vscode-pylance ms- 2021.6.3
jupyter ms- 2021.6.999662501
remote-ssh ms- 0.65.7
remote-ssh-edit ms- 0.65.7
vsliveshare ms- 1.0.4498
A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt678:30270856
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551cf:30311713
vspre833:30321513
pythonptprofiler:30281270
vshan820:30294714
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30323308
vscorehov:30309549
vscod805cf:30301675
binariesv615:30325510

@sbatten
Copy link
Member

sbatten commented Jul 6, 2021

This is possibly caused by extension, assigning to @alexdima to determine if its possibly us.

@alexdima
Copy link
Member

Moved to microsoft/live-share#4353

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants