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

Cannot open detected link #21126

Closed
alexdima opened this issue Feb 22, 2017 · 4 comments
Closed

Cannot open detected link #21126

alexdima opened this issue Feb 22, 2017 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@alexdima
Copy link
Member

Testing #21021

  • Open linkComputer.test.ts
  • Add at the bottom:
/**
 * .\languageSelector.test.ts
 * ..\modes\languageSelector.test.ts
 */
  • In the terminal cd src\vs\editor\test\common\modes
  • In the terminal cat .\linkComputer.test.ts
  • The links are detected but clicking on them appears to not do anything.
    terminal-links
@Tyriar
Copy link
Member

Tyriar commented Feb 22, 2017

@alexandrudima the links are resolved relative to the opened folder in VS Code, not the cwd of the terminal. A solution to the latter is being explored in #20676

Did you have the vscode directory open?

@Tyriar Tyriar added this to the February 2017 milestone Feb 22, 2017
@Tyriar Tyriar added the info-needed Issue requires more information from poster label Feb 22, 2017
@alexdima
Copy link
Member Author

Yes, I had C:\Alex\src\vscode opened and (as explained in the original steps) I did:

  • cd src\vs\editor\test\common\modes
  • cat .\linkComputer.test.ts

I see it is hard to say what should be considered the base. If we use the workspace path as the base, then perhaps interpreting ..\ links does not make a lot of sense (going outside the workspace). There is also the question of what to do when no folder is opened. In any case, a message when clicking fails might be better than doing nothing.

@Tyriar
Copy link
Member

Tyriar commented Feb 22, 2017

Until #20676 is looked into we don't have access to the shell's current working directory so this is blocked on that.

On empty workspaces, I've been thinking about the idea of validating the links before adding them to the DOM. It's probably a good idea, to avoid possible performance relayout issues from editing the DOM, a class could be added to indicate the link is invalid. I'll track that in #21226

@Tyriar Tyriar modified the milestones: Backlog, February 2017 Feb 23, 2017
@Tyriar Tyriar added terminal General terminal issues that don't fall under another label feature-request Request for new features or functionality and removed info-needed Issue requires more information from poster labels Feb 23, 2017
@Tyriar Tyriar closed this as completed Apr 21, 2017
@Tyriar Tyriar added *duplicate Issue identified as a duplicate of another issue(s) and removed feature-request Request for new features or functionality terminal General terminal issues that don't fall under another label labels Apr 21, 2017
@Tyriar
Copy link
Member

Tyriar commented Apr 21, 2017

Links are now validated (however there is a discussion to remove this for perf reasons #25024).

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants