Vscode: Terminal search results paths not clickable

[decodekult]

Running Visual Studio Code 1.27.1 over Windows 10, using Git bash as terminal and with ACK installed.

Up until the last update, after performing a term search in the terminal, Ctrl+click over paths in results opened the related file in a new tab. AFter the last update, that shortcut no longer works.

Tested also with PowerShell and the native Windows command line.

[Tyriar]

Can you share a screenshot? Also what folder was the terminal opened at initially?

[xackery]

1.27 over OSX, project links of e.g.
test/foo/file.go:12:12: some error here

used to be cmd+click able, now they don't show up as valid urls to click.
test/foo/file.go is relative to the project workpath root directory.

Absolute paths however are working

[decodekult]

Attaching a screenshot, with the path where the terminal opened, and the unclickable relative paths. No space in any of them.

[mceachen]

Confirmed on Mac, Windows, and Linux. This is a huge usability regression, unless you always write code that compiles the first time.

Note that this affects tsc/tsc --watch build terminals as well.

To reproduce, clone any typescript project and open it in vscode (like exiftool-vendored), ctrl-shift-b, pick tsc --watch, edit a file and create a syntax error. In all prior builds < 1.27 you've been able to click the filename in the tsc output terminal to jump to that file (and line) in your workspace where the error was found. In this build, the filenames are not clickable.

I'm running vscode 1.27.1 on windows 10, mac OS X 10.11, and Ubuntu 18.04.01.

[xackery]

this is a duplicate of #58256 i believe and #58232