Open anandijain opened 1 year ago
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!
possible duplicate of #93826, which technically got closed as wont-fix, but instead got closed as a duplicate of #34442.
i see some open issues on checking if the terminal is focused. apologies if there's overlap.
i often run the shell command
code ...
to open up files and folders. i write in julia, and julia has a nice function callededit
that allows me to open the specific method that will be called based on type information.there is another tool (Chthulhu.jl) facilitates traversing the call tree and uses this
edit
function to allow users to open the code of the current method. one slight annoyance is that vscode focuses the text editor by default whencode myfile.jl
is called.this makes a lot of sense in many cases, but when traversing the call tree, I typically just want to see the code, and less often want to edit it.
focusing the editor means having to do (ctrl+~) each time you traverse the tree, which takes me out of "the flow" i realize that expanding the scope of what the
code
cli command could do could very well be a slippery slope.so i don't know anything about vscode internals nor how feasible implementing it would be, but it would make the debugging experience in julia magical!
here is a little video that demonstrates needing to refocus the terminal each time i descend/ascend the call tree
https://user-images.githubusercontent.com/33790004/207106379-f20f510a-0b18-400f-ad7f-7dc989b86352.mp4
thank you for vscode! i love it