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 jump to file from Integrated Terminal #7321

Closed
ucirello opened this issue Jun 7, 2016 · 8 comments · Fixed by #20582
Closed

Cannot jump to file from Integrated Terminal #7321

ucirello opened this issue Jun 7, 2016 · 8 comments · Fixed by #20582
Assignees
Labels
feature-request Request for new features or functionality terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@ucirello
Copy link

ucirello commented Jun 7, 2016

  • VSCode Version: 1.2
  • OS Version: OS X

Steps to Reproduce:

  1. Open the terminal and make a compilation error in your favorite language
  2. Click on the file name it won't jump to the chosen file.
--> Monitor: Files changed, Building...
go build -v -i
github.com/REDACTED/REDACTED-ms/REDACTED
REDACTED/crumb.go:223: undefined: rpcCall

When selecting and clicking on REDACTED/crumb.go:223 it won't jump to the file.

Check how iTerm2 and ACME addresses this issue.

@Tyriar Tyriar added feature-request Request for new features or functionality terminal General terminal issues that don't fall under another label labels Jun 7, 2016
@Tyriar Tyriar self-assigned this Jun 7, 2016
@TurkeyMan
Copy link

TurkeyMan commented Jun 8, 2016

👍 Do want!
Clicking on errors should jump to the error like in any regular output window.

@tht13
Copy link
Contributor

tht13 commented Jun 9, 2016

The latest insiders build has a command workbench.action.terminal.focus which is both available in the F1 command palette under "Focus Terminal" and available to attach to a keybinding.

@ucirello
Copy link
Author

ucirello commented Jun 9, 2016

@tht13 what you said does not address the issue.

@tht13
Copy link
Contributor

tht13 commented Jun 9, 2016

Apologies, I'm not sure why I thought that was relevant

@Tyriar
Copy link
Member

Tyriar commented Jul 5, 2016

Doing this will likely be based on xterm.js' linkify addon which is currently not production ready. So this is blocked on xtermjs/xterm.js#27

@Tyriar Tyriar added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Jul 5, 2016
@kaiserdan
Copy link

kaiserdan commented Jul 30, 2016

This would especially be handy for js stack traces

@Tyriar
Copy link
Member

Tyriar commented Nov 21, 2016

Keeping this open to track as there will be some integration work to do once it's implemented upstream.

@Tyriar
Copy link
Member

Tyriar commented Jan 3, 2017

I gave an update to this in #17897 (comment):

My plan with linkify was to wait until it's worked out upstream either by myself or another contributor and then mold it so it works with VS Code. This may need to be put into xterm.js' core depending on how it performs. Also simply enabling addons will not just let it work as xterm.js is build for the browser, not electron. linkify adds <a> tags which will need to be handled specially within VS Code and thus will need tighter integration.

@Tyriar Tyriar mentioned this issue Feb 21, 2017
2 tasks
@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
feature-request Request for new features or functionality terminal General terminal issues that don't fall under another label upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants