Looking a little closer so it's working find without the ./ as mentioned in the report. This is because the full link text is being included as a link candidate along side the ones with the badly detected line/col numbers. So first thing I would investigate is why the full file isn't being parsed out as a link candidate when the ./ prefix is included.

The fallback case where the quick pick shows up (search opener) isn't as important since if this is a file it should have been validated.

Yeah, something is wrong with linkCandidates, even when link gets opened with search type. For both with and without ./ though.

Testing these:

None of links in pics worked🥲, even without the ./ Pre-PR.

I thought the reason why the negative lookbehind or removing the pre-existing (?::|#| |['"],|, )${r()}([:.]${c()}(?:-(?:${re()}\\.)?${ce()})?)? + eolSuffix,` was because the ISO 8601 format got picked up with that pre-existing regex.

Lists in link candidates array seem odd because it would get picked up by (?::|#| |['"],|, )${r()}([:.]${c()}(?:-(?:${re()}\\.)?${ce()})?)? + eolSuffix,` without the negative lookbehind.

Debugging (pre-PR)

2025-11-21 20:51:15.806 [trace] [8efa26f] terminalLocalLinkDetector#detect linkCandidates [["/Users/anthonykim/Desktop/Skeleton/test-2025-04-28T11"]]

and

2025-11-23 21:52:07.343 [trace] [8efa26f] terminalLocalLinkDetector#detect linkCandidates [["/Users/anthonykim/Desktop/Skeleton/test-2025-04-28T11:03:09+02"]]

After this PR atm with negative lookbehind I still get:

2025-11-23 22:16:48.551 [trace] [8efa26f] terminalLocalLinkDetector#detect linkCandidates [["/Users/anthonykim/Desktop/Skeleton/test-2025-04-28T11"]]

but I'm able to open the links with search type:

2025-11-23 21:56:29.921 [debug] [8efa26f] Opening link [{"text":"./test-2025-04-28T11:03:09+02:00.log","bufferRange":{"start":{"x":1,"y":12},"end":{"x":36,"y":12}},"type":"Search","contextLine":"./test-2025-04-28T11:03:09+02:00.log"}]

Ideally I think they should be localFile like this one:

2025-11-23 21:57:05.454 [debug] [8efa26f] Opening link [{"text":"./testFile.py","uri":{"$mid":1,"path":"/Users/anthonykim/Desktop/Skeleton/testFile.py","scheme":"file"},"bufferRange":{"start":{"x":59,"y":13},"end":{"x":71,"y":13}},"type":"LocalFile","parsedLink":{"path":{"index":58,"text":"./testFile.py"}}}]

I should figure out why link candidate is wrong for both pre/post this this PR like suggested above, and maybe that would get us localFile link instead of search!