Accepting ghost text left "No suggestions" box and inaccessible lines

[digitarald]

Type: Bug

I had a Copilot ghost text that I could not accept with tab. Tab would actually add characters into the document, pushing out the ghost text.

Once I hit Accept in the ghost text overlay, the "No suggestions" stayed around and the cursor can't be moved up/down anymore with keys, just left/right.

VS Code version: Code - Insiders 1.82.0-insider (35be9bf683eace09796e59d54f1f225bbc3a7866, 2023-08-30T05:35:06.924Z) OS version: Darwin x64 22.6.0 Modes:

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled| |Load (avg)|3, 2, 2| |Memory (System)|64.00GB (7.56GB free)| |Process Argv|--log trace --crash-reporter-id 4cf0a6f0-aaf8-4da3-9b2b-81f6c639c12b| |Screen Reader|no| |VM|0%|

Extensions (69)

Extension|Author (truncated)|Version ---|---|--- html-snippets|abu|0.2.1 Bookmarks|ale|13.4.1 tsl-problem-matcher|amo|0.6.2 docs-view|bie|0.0.11 emojisense|bie|0.10.0 github-markdown-preview|bie|0.3.0 markdown-checkbox|bie|0.4.0 markdown-emoji|bie|0.3.0 markdown-footnotes|bie|0.1.1 markdown-mermaid|bie|1.19.0 markdown-preview-github-styles|bie|2.0.2 markdown-yaml-preamble|bie|0.1.0 esbuild-problem-matchers|con|0.0.2 vscode-eslint|dba|2.4.2 githistory|don|0.6.20 kusto|don|0.4.4 gitlens|eam|2023.8.3005 EditorConfig|Edi|0.16.4 prettier-vscode|esb|10.1.0 auto-close-tag|for|0.5.14 auto-rename-tag|for|0.1.10 codespaces|Git|1.15.0 copilot|Git|1.106.371 copilot-chat|Git|0.7.2023083001 copilot-labs|Git|0.15.1019 remotehub|Git|0.61.2023081601 vscode-github-actions|git|0.26.1 vscode-pull-request-github|Git|0.71.2023083018 github-security-alerts|los|0.0.4 cortex-debug|mar|1.12.0 debug-tracker-vscode|mcu|0.0.15 memory-view|mcu|0.0.23 peripheral-viewer|mcu|1.4.6 rtos-views|mcu|0.0.7 theme-monokai-pro-vscode|mon|1.2.1 vscode-azurefunctions|ms-|1.12.4 vscode-azureresourcegroups|ms-|0.7.5 vscode-docker|ms-|1.26.0 vscode-dotnet-runtime|ms-|1.7.2 isort|ms-|2023.11.12061012 python|ms-|2023.15.12421005 vscode-pylance|ms-|2023.8.51 jupyter|ms-|2023.8.1002441100 jupyter-keymap|ms-|1.1.2 jupyter-renderers|ms-|1.0.17 remote-containers|ms-|0.307.0 remote-ssh|ms-|0.106.2023083015 remote-ssh-edit|ms-|0.86.0 remote-wsl|ms-|0.81.0 anycode|ms-|0.0.72 azure-account|ms-|0.11.5 azure-repos|ms-|0.37.2023082201 cpptools|ms-|1.17.5 live-server|ms-|0.4.9 remote-repositories|ms-|0.38.1 remote-server|ms-|1.5.2023082209 vscode-github-issue-notebooks|ms-|0.0.129 vscode-markdown-notebook|ms-|0.0.26 vscode-selfhost-test-provider|ms-|0.3.16 vscode-typescript-next|ms-|5.3.20230830 vsliveshare|ms-|1.0.5883 vscode-xml|red|0.26.1 vscode-yaml|red|1.14.0 kuskus-kusto-syntax-highlighting|ros|1.2.0 rest-book|tan|6.2.1 fugio|Tyl|0.0.4 vscode-mdx|uni|1.4.0 footsteps|Wat|0.5.0 markdown-all-in-one|yzh|3.5.1 (1 theme extensions excluded)

[jrieken]

@digitarald Do you have repro steps?

[digitarald]

@jrieken no, and logs also were void of anything related. I hit the tab-indents-ghosttext-but doesn't-accept before; but can't repro a second time afterwards.

[jrieken]

No, special keybindings or settings in this area?

[digitarald]

@jrieken nope, double-checked

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[vscodenpa]

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.

Happy Coding!

[vscodenpa]

We closed this issue because we are unable to reproduce the problem with the steps you describe. Chances are we've already fixed your problem in a recent version of VS Code. If not, please ask us to reopen the issue and provide us with more detail. Our issue reporting guidelines might help you with that.

Happy Coding!