When clicking the link, the correct file opens but at row 1.
Before installing the most recent update, this was buggy (jumping to the wrong row), now it doesn’t work at all. Or maybe you decided it’s better to not support it at all than leave it in the buggy state?
Steps to Reproduce
Have output like this in the terminal:
× eslint(no-plusplus): Unary operator ‘++’ used.
╭─[extension/src/indexer/chunker.ts:87:55]
86 │ hasMerge = false;
87 │ for (let i = 0; i < preliminaryChunks.length - 1; i++) {
· ───
88 │ const current = preliminaryChunks[i]!;
╰────
help: Use the assignment operator += instead.
Click on the file link.
Expected Behavior
Opens the correct file, jumps to the correct line.
I tried to reproduce this on macOS (Cursor 2.6.x), and the links work fine. Clicking ,-[file:line:col] in the oxlint output jumps to the right line. So this might be Windows-specific.
Quick question to narrow it down. Does this only happen with the oxlint output format (,-[file:line:col]), or do normal file links like extension/src/indexer/chunker.ts:87:55 also open at line 1 when you click them in the terminal?
That’ll help us tell if this is a general Windows terminal link parsing issue or something specific to the oxlint output format.
Hm, they do generally work, even with color. I tried running console.log("foo \x1b[1;34m ╭─[extension/src/indexer/chunker.ts:87:55]\x1b[0m bar");
I’ve noticed two more things that are at least different to vscode behavior. Maybe that could help narrow down where things might happen? Which is:
With simple console log, the link doesn’t get underlined on hover. (But it does when running oxlint in Cursor. And it does in all cases in vscode.)
When clicking the link from console log, it opens the file picker menu because there’s also chunker.test.ts. (This doesn’t happen with oxlint output. It doesn’t happen in all cases in vscode.)
I also realized that when the files are opened without jumping to the correct line, they are actually opened to the last known cursor position. Which had me quite confused during testing just now because I would use console log, go to the correct position and all of a sudden, it seemed to work with oxlint. No, Cursor just still had it stored from when I clicked the console log link.