nvimdev / nvimdev/lspsaga.nvim

Buffer opened with incorrect layout right after peeking the source code

Open
#1,426 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Lua
Stars
3.8k
Forks
308
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Hi,

When I jump to the definition (:Lspsaga goto_definition) of symbol right after peeking the source of that symbol, the buffer is opened with the layout of the peek window (black background; no line numbers) instead of the default layout (dark blue background, with line numbers.

Example:

  • [Peek definition of watch_and_process_build]: black background; no line number
peek
  • Buffer opened right after peeking (actual behavior): black background; no line number (see right side in image)
actual
  • Buffer opened without peeking (expected behavior): dark blue background, with line numbers
expected

I am using nvim-10.0 (also tried 0.95) with the latest version of Lspsaga.

Any idea why this happened and how this could be fixed?

Thanks!
Christof

Steps to reproduce

See example above

Expected behavior

See example above

Neovim version (nvim -v)

0.10

lspsaga commit

f20985499cd8ff0fbbfe8e7c770428ef764fc3be

Terminal name/version

ITerm 3.4

Contributor guide

No contributing guide indexed for this repository

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 sequence in Neovim: peek a definition, then run :Lspsaga goto_definition, and compare it with opening the definition directly. Done means the buffer opened after peeking uses the default layout, including its background and line numbers.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.