-
Notifications
You must be signed in to change notification settings - Fork 29.2k
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
Resolve relative REPL paths #15464
Resolve relative REPL paths #15464
Conversation
@felixfbecker, thanks for your PR! By analyzing the history of the files in this pull request, we identified @isidorn, @bpasero and @egamma to be potential reviewers. |
Usage looks good to me -> merging in. |
Absolute paths are broken now
Seems like the context service cannot resolve paths that are already absolute. |
@felixfbecker thanks for fixing and testing this feature - you are doing the whole cycle :) It seems like we should include node 'path' and perform this check https://nodejs.org/api/path.html#path_path_isabsolute_path Let me know if you are on it, if not no worries I can push it as well. |
I'm always running on Insiders, and need to click on links in the REPL on a minutely basis 😉 I though about using
Btw I'm a bit surprised everything works correctly in the output panel, but not in the REPL - shouldn't they share the same code for stuff like this? |
@felixfbecker yes, perfectly that code would be shared. I could actually look into that refactoring next week. |
Another improvement that I would like, currently the terminator |
And it would be so awesome if the REPL had the same features as the output panel - especially finding and selecting more than one page of text. At the same time the output panel should have the CLI color support of the REPL. |
The problem with aligning repl and output lies in the fact the repl is using a tree as an implemenation detail and output an editor. You can read up more about this here #11462 |
@bpasero is this the correct usage? Still cannot build + test
#13370