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
{{ message }}
Repository navigation
Cannot jump to search result in text editor when CSV extension is enabled #104
Normally if I open the search panel via Search: Find in Files command in VSCode, I can search somthing and click one of the results to jump to that line. But it currently doesn't work in a csv file with CSV extension enabled. When I click the result, the cursor seems jump back again after it jumps to the destinated line.
Jump to line works properly in other types of file (eg. plain text file. I have not test tsv or other table types yet). I open the text editor by running CSV: Toggle Extension On/Off. After disabling the CSV extension in VSCode extension managment panel, the search function can work properly.
I recorded a video to better demonstrate that:
I'm using VSCode v1.103.2, with CSV extension v1.3.0
Thank you for the detailed report and for checking the behavior with the extension disabled. I’m sorry it’s interfering with searching. Related fixes are underway in #110, though I haven’t yet confirmed they resolve your full example. As I mentioned in on your other post, I appreciate your patience and the care you’ve taken to help.
I rebuilt the plugin using the latest code from the codex/fix-editor-navigation branch, but I'm still seeing the issue on my end — not sure if I missed a step. Please let me know if there's anything I can help with.
The update fixes native search routing when CSV is Off and, for supported saved local files, after choosing Text. Those paths were checked in an installed VS Code host, including restart. A cold result into a file still using Table can still miss the destination, and some remote/virtual paths cannot use the per-file Text association. I am keeping this open with #127 for those remaining cases; choosing Text or turning CSV Off is the current workaround.
Audit note: Partial: Off and explicit local Text choice fixed. Remaining work: Keep explicit supported saved-local Text choice and Off native routing; separately implement/prove native match handoff for still-Table/cold opens and unsupported URI contexts. Track cold investigation in #127.
Activity
jonaraphael commentedon Oct 17, 2026
Thank you for the detailed report and for checking the behavior with the extension disabled. I’m sorry it’s interfering with searching. Related fixes are underway in #110, though I haven’t yet confirmed they resolve your full example. As I mentioned in on your other post, I appreciate your patience and the care you’ve taken to help.
li-zyang commentedon Oct 17, 2026
Thanks for the quick reply!
I rebuilt the plugin using the latest code from the
codex/fix-editor-navigationbranch, but I'm still seeing the issue on my end — not sure if I missed a step. Please let me know if there's anything I can help with.Keep explicit text views for native search results (#104)
jonaraphael commentedon Oct 17, 2026
The update fixes native search routing when CSV is Off and, for supported saved local files, after choosing Text. Those paths were checked in an installed VS Code host, including restart. A cold result into a file still using Table can still miss the destination, and some remote/virtual paths cannot use the per-file Text association. I am keeping this open with #127 for those remaining cases; choosing Text or turning CSV Off is the current workaround.
Audit note: Partial: Off and explicit local Text choice fixed. Remaining work: Keep explicit supported saved-local Text choice and Off native routing; separately implement/prove native match handoff for still-Table/cold opens and unsupported URI contexts. Track cold investigation in #127.