lapce / lapce/lapce

Code Action Context Menu: Cannot Open Code Action Menu with Right-Click, Click Lightbulb, or `Ctrl+.` hotkey

Open
#286 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-lsp A-ui C-bug
Dominant language
Rust
Stars
38.9k
Forks
1.3k
Avg merge
19m
Merged PRs (30d)
1

Description

Platform: Windows
Lapce Version: commit d9b0492267c786af8314bfce8b87673a130bf86c, built from latest on master

Repro Steps

  1. Leave the cursor on an actionable symbol,
  2. a lightbulb appears in the sidebar
  3. Press Ctrl+. (may not be reflected in the video, just do this at any point)
  4. drag the cursor outside the text editor and back

Expected: Any of
A. Right-clicking an actionable symbol,
B. Left-clicking the Lightbulb in the sidebar,
C. or using hotkey Ctrl + . while the cursor is on an actionable symbol
opens the code action context menu immediately

Actual: pressing Ctrl+. , then dragging the cursor outside the text editor window and back opens the code action context menu.

https://user-images.githubusercontent.com/1480323/160231348-a84471bf-2cec-42f8-818c-c1d7b7cc0671.mp4

Shorter video

https://user-images.githubusercontent.com/1480323/160231558-018c3d07-d083-47c0-af9d-0c08a2dac3d9.mp4

Sample Source:

let index = std::cmp::min(0, 15);
		
// timing mea timing measures for Frames-Per-Second
use std::time::Instant;
let now = Instant::now();
let mut time_fence = index; // the previous second that has been printed.
let mut count = index; // count of frames

In this context, the option to inline index should be available to replace the two usages of it with the function call.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows behavior using the listed steps and sample Rust source, checking the right-click, lightbulb, and Ctrl+. paths separately. Trace the code-action context-menu entry points and compare them with the described drag-out-and-back behavior; done means each trigger opens the menu immediately.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.