Skip to content

[Feat] Column inverse search#28

Draft
DavidLapous wants to merge 4 commits into
f3fora:masterfrom
DavidLapous:test_col
Draft

[Feat] Column inverse search#28
DavidLapous wants to merge 4 commits into
f3fora:masterfrom
DavidLapous:test_col

Conversation

@DavidLapous

Copy link
Copy Markdown

I just added this to test this feature, but okular / zathura seem to always return 0 or -1 for the column, which is quite sad.
Do you have an idea why this doesnt work ?

Fixes #27 (up to a working editor).

@f3fora

f3fora commented Apr 22, 2025

Copy link
Copy Markdown
Owner

I have no idea why they return always 0 or -1.
Hovever, builtin texlab inverse search command and vimtex do not use the column data.

You can try to investigate.

@DavidLapous

Copy link
Copy Markdown
Author

I have no idea why they return always 0 or -1.

I'll try to find a working editor when I'll have time, e.g., kile which was working for me at some point

Hovever, builtin texlab inverse search command and vimtex do not use the column data.

Does texlab has something to do with the inverse search ? As far as I understand this process, the pdf editor looks at the synctex info, recovers the line and then (up to some config) calls your go program to send the line to neovim. Am I missing something?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[feat] Support for column variable in inverse search

2 participants