-
Notifications
You must be signed in to change notification settings - Fork 4
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
[Feedback] new CallStack feature #10
Labels
Comments
RedCMD
added a commit
that referenced
this issue
Apr 13, 2024
RedCMD
added
enhancement
New feature or request
question
Further information is requested
labels
Apr 16, 2024
|
RedCMD
added a commit
that referenced
this issue
May 6, 2024
RedCMD
added a commit
that referenced
this issue
May 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I've just add a new feature. CallStack (name change?)
just install the latest pre-release version
open any basic document and right click =>
Show TextMate Calling Stack
It'll open up a new view showing you the tree structure of how TextMate tokenized the file
each element is a
begin
ormatch
rulewith the label being
name
most things are wip
while
,end
andcaptures
don't show up correctlyI am yet to implement the
Follow Cursor
featurebut the goto feature is mostly working so far
just click the little right arrow on an element and it'll take you to the corresponding rule
what icon should I have for each element?
prob something different for begin/match/end/while/captures etc
for the label
should I use
name
,contentname
,comment
, or the captured text?being in mind that any of them could be blank
more so in different grammars
annoyingly I had to modify the original vscode-textmate code to be able to extract the textmate tree structure
I was thinking of using https://github.com/ds300/patch-package instead of including the entire vscode-textmate repo
does the patch package tool work well on 50k+ character single line files?
currently
many bugs
The text was updated successfully, but these errors were encountered: