You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the correct behavior of Swiper, with either visual-line-mode and/or lsp-lens-mode disabled.
I search for the term QueryParam and it highlights the two occurrences. I can jump to either occurrence:
Now I enable visual-line-mode and lsp-lens-mode.
Here are two Lenses which add up to about 30 lines:
I search for QueryParam again. The two instances are correctly highlighted. However, jumping lands on the wrong location. The wrong location is offset by the lines of the lenses. Here is jumping to the first occurrence of QueryParam:
It appears that
visual-line-mode
andlsp-lens-mode
(https://github.com/emacs-lsp/lsp-mode/blob/master/lsp-lens.el) have an effect on Swiper.Both
visual-line-mode
andlsp-lens-mode
must be enabled to demonstrate this.Here is the correct behavior of Swiper, with either
visual-line-mode
and/orlsp-lens-mode
disabled.I search for the term
QueryParam
and it highlights the two occurrences. I can jump to either occurrence:Now I enable
visual-line-mode
andlsp-lens-mode
.Here are two Lenses which add up to about 30 lines:
I search for
QueryParam
again. The two instances are correctly highlighted. However, jumping lands on the wrong location. The wrong location is offset by the lines of the lenses. Here is jumping to the first occurrence ofQueryParam
:And the second occurrence:
Here is the file: https://github.com/peterbecich/servant-ekg/blob/6dc27930c34f38ee391a1d4d57dc436438abddd0/lib/Servant/Ekg.hs#L120
These screenshots were produced with an isolated environment,
lsp-start-plain
.Built-in
I-search
is unaffected by this. Do you think it is better to open this issue in https://github.com/emacs-lsp/lsp-mode?This issue is similar but smaller, and does not pertain to Swiper: emacs-lsp/lsp-mode#3329 But I wonder if the underlying cause may be the same.
Thank you
The text was updated successfully, but these errors were encountered: