Skip to content

Add hats to tokens in the outline pane #568

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

Closed
DanGoesIntercept opened this issue Feb 15, 2022 · 3 comments
Closed

Add hats to tokens in the outline pane #568

DanGoesIntercept opened this issue Feb 15, 2022 · 3 comments

Comments

@DanGoesIntercept
Copy link

DanGoesIntercept commented Feb 15, 2022

It would be very useful to have elements in the outline pane of Visual Studio Code get hats so that when I want to bring them into code, they are targetable like other in-buffer tokens. The token in the outline pane could be treated either as exactly what is listed within the pane (e.g. _someVariable, or Start()), or it could be the full statement that the outline element represents. This would allow you to bring, move, go to, and other actions that makes sense.

@pokey
Copy link
Member

pokey commented Feb 16, 2022

Hi @DanGoesIntercept! Yes, that would be awesome. Unfortunately, the VSCode api can be quite limiting. We don't have the ability to put hats in that part of the editor using the VSCode api 😕

The closest we are likely to be able to get is #423

Longer term, we'll probably be able to get there along a more generic route using either OCR or the accessibility tree, but both of those will require new functionality from talon, esp if we want them to operate cross-platform

@DanGoesIntercept
Copy link
Author

Well that's disappointing, but make sense. Thanks for the response. This at least gives me a good reason to poke a bit through the source code for vscode & cursorless to see how it all fits together!

@pokey
Copy link
Member

pokey commented Feb 16, 2022

Yes, definitely a bummer; would love to have something like that myself. I want hats everywhere 😊

I think I'll close this one for now, but we can reopen it once we get OCR / accessibility tree stuff working

@pokey pokey closed this as completed Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants