[Bug] Global Search (ctrl/cmd+shift+f) does not traverse to the respective line of code

[notRyuk]

While using the global search vscode correctly identifies the search patterns but the markdown extension does traverse to the line/position of code when searching.
The following is an example:
https://github.com/user-attachments/assets/35a5c4f9-53fa-44df-95ec-c689e68440d1

This happens in both live & source mode.

---

Edit:
Running version: 0.1.12

[vadimmelnicuk]

@notRyuk thanks for reporting this. This is a known VS Code limitation where global search results open files through an internal path that does not forward the line/column selection to custom editors, meaning MEO never receives the position to scroll to. There is a workaround in progress and I will update this issue once it is available.
microsoft/vscode#289785

[notRyuk]

@vadimmelnicuk yeah i was going through the code since this is message based extension and the viewer is not a direct file interpreter we are not receiving the position/selection details on opening file (handleInit)

[vadimmelnicuk]

@notRyuk thanks for digging into the code and confirming that. As a workaround until VS Code exposes an API for this, you can open the file normally first and then use "Find in File" (Cmd+F) to locate the specific line. Closing this issue for now since there is no fix available on our end, but it will be revisited once the VS Code API supports it.