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

Pressing Ctrl+Enter does not accept copilot suggestion #5510

Open
strowk opened this issue Feb 21, 2025 · 0 comments
Open

Pressing Ctrl+Enter does not accept copilot suggestion #5510

strowk opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
triage-needed Issues needing to be assigned to the prospective feature owner

Comments

@strowk
Copy link

strowk commented Feb 21, 2025

Type: Bug

Steps to Reproduce:

  1. Go to Copilot Edits chat
  2. ask it to do something
  3. after suggestion appeared press Ctrl+Enter
    expected: suggestion applied
    actual: it opens another GitHub Copilot Suggestions panel

No other buttons are pressed, UX expectation here is that edit should be possible to accept without using mouse, just on keyboard. Reality is that I have to press this tiny Accept button with my mouse even though it claims to work on Ctrl+Enter

Extension version: 0.24.1
VS Code version: Code 1.97.2 (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z)
OS version: Linux x64 6.8.0-52-generic snap
Modes:

Prompt Details
Info: Using the Electron fetcher.
Info: Initializing Git extension service.
Info: Successfully activated the vscode.git extension.
Info: Enablement state of the vscode.git extension: true.
Info: Successfully registered Git commit message provider.
Info: Logged in as strowk
Debug: [context keys] Updating context keys.
System Info
Item Value
CPUs AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (16 x 3122)
GPU Status 2d_canvas: unavailable_software
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
webnn: unavailable_software
Load (avg) 4, 4, 5
Memory (System) 60.63GB (47.80GB free)
Process Argv --no-sandbox --force-user-env --crash-reporter-id 095edecf-8ad9-4c12-a945-68f9e160e22f
Screen Reader yes
VM 0%
DESKTOP_SESSION ubuntu-xorg
XDG_CURRENT_DESKTOP Unity
XDG_SESSION_DESKTOP ubuntu-xorg
XDG_SESSION_TYPE x11
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
iacca1:31171482
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31242946
customenabled:31241370
8did9651:31230678
9064b325:31222308
copilot_t_ci:31222730
jda6j935:31233686

@vs-code-engineering vs-code-engineering bot added the triage-needed Issues needing to be assigned to the prospective feature owner label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage-needed Issues needing to be assigned to the prospective feature owner
Projects
None yet
Development

No branches or pull requests

2 participants