Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v1.27.2] Source file links still not clickable. #59052

Closed
AlCalzone opened this issue Sep 20, 2018 · 7 comments
Closed

[v1.27.2] Source file links still not clickable. #59052

AlCalzone opened this issue Sep 20, 2018 · 7 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues windows VS Code on Windows issues

Comments

@AlCalzone
Copy link

Followup to #54788, #57987 and #58256
I'm using version v1.27.2 now and the issue still persists. This is a huge pain in a monorepo I'm currently working on. What more information can I provide you guys with to get this resolved?

cc @Tyriar

@Tyriar
Copy link
Member

Tyriar commented Sep 20, 2018

@AlCalzone

  1. What directory did you open the terminal in?
  2. Is the link you're pointing at relative to the directory the terminal was opened in?
  3. Can you provide a screenshot?

@Tyriar Tyriar added info-needed Issue requires more information from poster terminal Integrated terminal issues labels Sep 20, 2018
@AlCalzone
Copy link
Author

  1. like I wrote in Source file links not clickable in integrated terminal #57987 (comment), its a kinda long path with a space in it: C:\users\....\Something with space\Repositories\repo-name. This is the directory I open inside VSCode. I then press CTRL + ö (german version) to open the terminal in that directory.
  2. Yes, inside the directory is (among others) a directory src. I then run the typescript compiler, which finds an error in a file and prints a link to there: src/folder/filename.ts:1234:1. This link is not clickable.
  3. I'm currently on another machine where there's no space in the root directory name. Here it works:
    unbenannt
    I'll provide a screenshot from my other machine where its not working later today as I don't have access right now. Not sure how much that helps you though, as you won't see the underline or the tooltip.

@Tyriar
Copy link
Member

Tyriar commented Sep 21, 2018

@AlCalzone a screenshot would still be helpful, just make sure you launch the terminal in the same way. I don't think there is anything that would make directories with spaces in the path not work 🤔

@AlCalzone
Copy link
Author

unbenannt
Here you go. I opened VSCode with the current workspace, opened the terminal using the keyboard shortcut, and ran tsc twice. Before the 2nd time I introduced a compile error to get a message. There are no links in the terminal, except the absolute one pointing to the npm debug log.

Note that this test was done on a third machine, which also has spaces in the path. In fact it uses the same base directory as the first machine.

@Tyriar
Copy link
Member

Tyriar commented Sep 22, 2018

I can repro on Windows 7, everything seems to work fine until the path with the space in the root path appears. Also it doesn't appear to be related to the @ symbol or the line/col annotation but the spaces as you suggest.

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug windows VS Code on Windows issues and removed info-needed Issue requires more information from poster labels Sep 22, 2018
@Tyriar
Copy link
Member

Tyriar commented Sep 22, 2018

It's happening because this exec is returning the path before the first space and then goes on to fail validation:

https://github.com/Microsoft/vscode/blob/079518239fa8643678b74ef87fbe687ce760e3c7/src/vs/workbench/parts/terminal/electron-browser/terminalLinkHandler.ts#L304-L310

@Tyriar
Copy link
Member

Tyriar commented Sep 22, 2018

I think this issue will have to be solved when the link system is improved in #21125, I'll make a note over there about this case.

@Tyriar Tyriar closed this as completed Sep 22, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 22, 2018
Tyriar added a commit that referenced this issue Sep 22, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) terminal Integrated terminal issues windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

2 participants