@@teej_dv if only you would do a long length video about tree sitter, feels like you did though, like recently, ehhhh......guess not, must be losing it....BLAZINGLY CRAZY!
Your videos are impressive. I think the value comes from explaining one topic so one understands, how it works on an intuitive level while keeping the video short.
I never comment on any TH-cam videos.... but damn, this video was really great. Not only did you talk about an interesting topic but also explained it extremely well. Please keep on releasing more of these videos. We need content creators like you.
Haskell slander aside, this was amazing! I can't believe how much of ts you explained, along with giving clear usecases and examples right into vim. Thanks for putting this out!
I actually used tree-sitter in a project a while ago making a LS for a DSL. It worked pretty well and had auto-complete, hover, signature help, and syntax error highlights. However, tree-sitter's error recovery ability still remains a problem to make it a viable tool for creating LSs.
You really have a great way of explaining things in a way that anyone can understand, even beginners like myself - this was very interesting and informative, looking forward to the next explainer
I would love a more in depth video on writing grammar, and more specific scanner. Been diving into writing grammars lately and so appreciate the content!
Love this video. Recently had to edit the grammar for a semi-obscure language as it was missing features and loved how simple it was. I mean it still took me 4 hours because I didn't know anything about tree-sitter but I wish I saw this video before then, it would have been so much help! Keep it up!
TJ you're my new favorite youtuber/content creator. I really hope the full time thing works out for you, good luck. Definitely need more videos like these. Also now I hope you are able finish the interpreter in OCaml series one day :D
This is a great explainer on Treesitter. I used Atom in the past, switched to Vim then Neovim. I knew what treesitter did inside neovim, and heard that it is the best one at its job but never really understood what is soo good about it.
I still don't really know what I can do with tree-sitter, but now I know what and how it does this thing in Neovim : great knowledge sharing, thanx :-)
This was dense. I'll be honest, a lot of it went right over my head as I'm starting to learn now, but I hope to return in time and realize it all makes sense 😅. Great content, I love the educational stuff. Keep it up.
I hate the rest of the internet. Nobody else seemed to care about explaining what everything i was installing was doing and just that i should install it. This really, really sucks while ur trying to configure neovim on your own for the first time. Please keep it up < 3
I had the ideas but this really helped me connect them together… treesitter really is extremely powerful and I’m already getting ideas of cool things I could use it for if I learn it a bit
Oh, I have a new question - if tree sitter has no clue about context, it just parses text to ast. How does syntax highlighting working through tree sitter know when my identifier is a function or value? What I mean is when in TS I define a ``` const num = 5; function func(){} console.log(a, func) ; ``` It would highlight num blue and func yellow - how does it even know here that func is a function? From my understanding it would only know it's just some sort of identifier
The bit that I was really interested in is how the tree sitter determines what the “least number of errors” is for a given invalid program. Looks like it was never covered but I’m still curious.
I'm on the journey of configuring neovim from scratch, this is second video I watched, first one was about Abstract Syntax Tree. I think I would be able to set up neovim in under 100 hours. Probably a 5-8 videos more and after that practice for 80 hours. Then finally I would be able to use neovim how I like.
Very well explained. Although, as a Mac power user it's still hard to overcome all the entry barriers. It's too easy to forget all the needed fundamentals that are needed to switch to neo vim. (as an active freelancer working on projects)
Tresitter is clearly a tokenizer and lexical analyzer, on top of you have some productions that are general enough to build branches in the syntax tree such as braces aaround a list without committing to specific languages. Am I on the right track track here?
Some lsp clients implement syntax highlighting themselves, right? How does neovim decide on using treesitter or lsp highlighting? I would assume that treesitter takes precedence, since it's faster, but if lsp and treesitter are unrelated, then how does it work?
Great explanation .I had no idea I was building something that already existed , Iv been writing a language query system in rust ... I just have no interest in having to go back to C or train someone else in C to be able to use tree sitter building new language libraries for tree sitter to use . I'd love to know the learning curve with tree sitter when building a language parser for a new language that hasnt been done or shared with it .
@@teej_dvOK that sounds interesting , so basically tell it the syntax and structure or and using javascript to create a grammar , then I could use rust bindings if I wanted to read or compile that grammar into something consumable. I was under the impression I had to use C to write and compile that grammer into a library that uses C lib exports for bindings, so that I could then consume it with a Language like Rust or whatever Lang to be able to query what it parses... So it sounds like a 2 stage approach versus the 3 phase approach I was thinking . Which means I dont need to use C at all.
I could be wrong because some of the information went over my head, but it sounds like treesitter is a file syntax parser and NOT a babysitter for trees.
"LSP and Treesitter are unrelated" - but do LSPs use treesitter for text parsing for example? Like LS-server receives an event with file changes, it runs them through tree-sitter to get a parsed result and then based on AST it can generate a response to the client?
hello TJ, may I ask you something? While using VS Code, the Vim extension makes possible for me to use Visual Block mode, and then when I enter "I" to insert text, then backspace , the text follows for each line selected, and it is pretty good to use with SQL queries for example. When I try to do this with Vim or Neovim, I just can't, and I don't think it is the 'whichwrap' option, do you know what it is? Thank you.
Great video except I do infact delete the file everytime I want to change something. I run echo >> file.ml (ocaml BTW) every time I need to edit something. It's a more functional way to program. Having random, nonrecursive access to a character in a file, like having access to an element in an array introduces state into the writing of my program
Why does tree sitter sound like an insult
Treeshitter
Don't be such a tree sitter, man
It does sound like an insult xD
cuz of bush camper?😂
I stop before continuing watching. Thank God for having you. I want to know more about this treesitter. I hope we have series for treesitter.
hoping to do longer video later, will take some time to put together
@@teej_dv if only you would do a long length video about tree sitter, feels like you did though, like recently, ehhhh......guess not, must be losing it....BLAZINGLY CRAZY!
I mean you could read the docs. You'll know more than you ever could from watching videos. Reading documentation has become a superpower.
Your videos are impressive. I think the value comes from explaining one topic so one understands, how it works on an intuitive level while keeping the video short.
I never comment on any TH-cam videos.... but damn, this video was really great. Not only did you talk about an interesting topic but also explained it extremely well.
Please keep on releasing more of these videos. We need content creators like you.
Great stuff, keep it up your kickstart vid has helped me out a lot on getting back into Neovim fully.
Thanks!! glad to hear it :)
Haskell slander aside, this was amazing! I can't believe how much of ts you explained, along with giving clear usecases and examples right into vim. Thanks for putting this out!
I'm really jealous about the way this guy expresses ideas and concepts. Huge, huge fan!
The quality of each video you put out just gets better and better. Thank you!
This makes a lot more sense now. Really like how you break things down in a simple way. It makes it a lot easier to understand concepts.
Followed after the LSP video, and now I get this! The top quality explainers just keep coming! Thanks TJ!
Bless you for your fantastic explainers and all your work on Neovim. Huge fan!
I actually used tree-sitter in a project a while ago making a LS for a DSL. It worked pretty well and had auto-complete, hover, signature help, and syntax error highlights. However, tree-sitter's error recovery ability still remains a problem to make it a viable tool for creating LSs.
Pulled me in with the trees in the thumbnail, stayed for the solid explanations. Thanks man!
You really have a great way of explaining things in a way that anyone can understand, even beginners like myself - this was very interesting and informative, looking forward to the next explainer
What blows my mind is that it downloads some C files, COMPILES THEM and then runs them nice and fast and natively. Great stuff
blown away in peices after seeing this video, I'm still recovering. This is very impresive, I want to learn scheme now
Great video TJ! really enjoy how you break everything down, makes it easy to understand and learn
These videos are really great TJ, please keep them coming!
I would love a more in depth video on writing grammar, and more specific scanner. Been diving into writing grammars lately and so appreciate the content!
ya, might do longer video of this later -- will have to be way longer haha
First time in my life I feel like I understand what treesitter is. Hats off!
Great video, thanks!!! Just the right amount of depth and standing while presenting was extra engaging!
Love this video. Recently had to edit the grammar for a semi-obscure language as it was missing features and loved how simple it was. I mean it still took me 4 hours because I didn't know anything about tree-sitter but I wish I saw this video before then, it would have been so much help! Keep it up!
TJ you're my new favorite youtuber/content creator. I really hope the full time thing works out for you, good luck. Definitely need more videos like these. Also now I hope you are able finish the interpreter in OCaml series one day :D
Man this is dope. I never thought to try to understand LSPs and the parsers powering them. It was all just magic.
Incredible. Cleared up a ton of confusion for me. Thank you!
I didn't know tree-sitter uses JDSL, Tom is indeed a genius
This is a great explainer on Treesitter. I used Atom in the past, switched to Vim then Neovim. I knew what treesitter did inside neovim, and heard that it is the best one at its job but never really understood what is soo good about it.
You're a truly gifted teacher among your many other talents.
I still don't really know what I can do with tree-sitter, but now I know what and how it does this thing in Neovim : great knowledge sharing, thanx :-)
Have never understood the REAL difference between LLM, LSP and treesitter. This video was very useful
This was dense. I'll be honest, a lot of it went right over my head as I'm starting to learn now, but I hope to return in time and realize it all makes sense 😅.
Great content, I love the educational stuff. Keep it up.
TJ your presentations skill is a masterpiece
Future Nile will admire you more than anyone.
Great video.
Ignore the spelling mistakes if any.
Amazing stuff Teej, keep it up!
Thanks :) :)
I really love this new wave of content from you champ 👍🏻
Godlike TJ, well done once again with the explanations, more of this!
I hate the rest of the internet. Nobody else seemed to care about explaining what everything i was installing was doing and just that i should install it. This really, really sucks while ur trying to configure neovim on your own for the first time. Please keep it up < 3
Really cool video. Thank you for showing us behind the curtain!
You know this video is going to be good when Teej brings out the blazer.
I had the ideas but this really helped me connect them together… treesitter really is extremely powerful and I’m already getting ideas of cool things I could use it for if I learn it a bit
So great to hear!! thanks for the nice words :)
Man your explanation sound great! Keep going!
What would we do without trees*itter
we would not be sitting on the trees
You are a good human, TJ.
This guy is a machine!! Def much better than that netflix-btw-guy
who ends his streams thinking we know his name))
Really good explanation, thank you for the knowledge!!!
Oh, I have a new question - if tree sitter has no clue about context, it just parses text to ast.
How does syntax highlighting working through tree sitter know when my identifier is a function or value?
What I mean is when in TS I define a
```
const num = 5;
function func(){}
console.log(a, func) ;
```
It would highlight num blue and func yellow - how does it even know here that func is a function? From my understanding it would only know it's just some sort of identifier
Great job man! Keep up the good work!
Thanks :)
Thank you for such an awesome explanation!
Great video, lots of cool tools built around the ecosystem like ast-grep
i am loving these videos. really great info!
The bit that I was really interested in is how the tree sitter determines what the “least number of errors” is for a given invalid program. Looks like it was never covered but I’m still curious.
I'm on the journey of configuring neovim from scratch, this is second video I watched, first one was about Abstract Syntax Tree. I think I would be able to set up neovim in under 100 hours. Probably a 5-8 videos more and after that practice for 80 hours. Then finally I would be able to use neovim how I like.
This was awesome. Thanks for the explanations!
To the point, simply brilliant
Very well explained. Although, as a Mac power user it's still hard to overcome all the entry barriers. It's too easy to forget all the needed fundamentals that are needed to switch to neo vim. (as an active freelancer working on projects)
Tresitter is clearly a tokenizer and lexical analyzer, on top of you have some productions that are general enough to build branches in the syntax tree such as braces aaround a list without committing to specific languages. Am I on the right track track here?
Nice stuff. You explain things really well.
What are the security implications of auto install of the different language parsers?
Well, that certainly was an excellent explanation of something I didn't know I needed to know. Thanks!
Maybe now I'll find out what an LSP is... ;-)
any chance you could do an indepth LSP video, i watched the dedicated one but would like to learn more about the capabilities and handlers
yes, i'm planning an entire video of writing a complete lsp from scratch
@@teej_dvthank you than you
Some lsp clients implement syntax highlighting themselves, right? How does neovim decide on using treesitter or lsp highlighting? I would assume that treesitter takes precedence, since it's faster, but if lsp and treesitter are unrelated, then how does it work?
Great video, thank you, TJ!
Great explanation .I had no idea I was building something that already existed , Iv been writing a language query system in rust ... I just have no interest in having to go back to C or train someone else in C to be able to use tree sitter building new language libraries for tree sitter to use .
I'd love to know the learning curve with tree sitter when building a language parser for a new language that hasnt been done or shared with it .
You don't write c when you use tree sitter. You write the grammar in js and you usually have language bindings already in other langs.
@@teej_dvOK that sounds interesting , so basically tell it the syntax and structure or and using javascript to create a grammar , then I could use rust bindings if I wanted to read or compile that grammar into something consumable.
I was under the impression I had to use C to write and compile that grammer into a library that uses C lib exports for bindings, so that I could then consume it with a Language like Rust or whatever Lang to be able to query what it parses...
So it sounds like a 2 stage approach versus the 3 phase approach I was thinking . Which means I dont need to use C at all.
I could be wrong because some of the information went over my head, but it sounds like treesitter is a file syntax parser and NOT a babysitter for trees.
Omg, what a great explanation!
Great video and explanation as always
Bro it's late and I was like "tree sitter ? Wtf would you like someone to watch over a tree for you ?" and I feel very stupid now
how did you got TS query window open? I found the way to open right tree window with :InspectTree command
was wondering this too. it's :EditQuery but looks like it's a 0.10 feature
"LSP and Treesitter are unrelated" - but do LSPs use treesitter for text parsing for example? Like LS-server receives an event with file changes, it runs them through tree-sitter to get a parsed result and then based on AST it can generate a response to the client?
not generally no. they usually use hand-rolled custom parsers that are optimized for their language
"isn't that outdated and illegal now" not proud to understand that joke because i'm chronically online
Sharp sports coat, very professional!
hello TJ, may I ask you something?
While using VS Code, the Vim extension makes possible for me to use Visual Block mode, and then when I enter "I" to insert text, then backspace , the text follows for each line selected, and it is pretty good to use with SQL queries for example. When I try to do this with Vim or Neovim, I just can't, and I don't think it is the 'whichwrap' option, do you know what it is? Thank you.
You can, by typing `dd`
LISP MENTIONED LISP MENTIONED LISP MENTIONED LISP MENTIONED LISP MENTIONED
Vscode seem to be discussing potentially moving to treesitter from textmate grammars, it'll be a loooong time though.
can you make video about c# + tree sitter? please
How to build a parser, I need parser for Razor pages
you should try a different material sports coat. Tweed or Linen perhaps
Eloquently explained!
Um ackshually: treesitter and LSP overlap w.r.t. semantic highlighting
You said tree-sitter is not an LSP, but could you use tree-sitter to implement an LSP sort of thing on top of it?
Guys what is he using for presentation ?
Where is the video on LSPs?
this looks like a logical expression query language 10:48
Is this like a baby sitter but for trees
Great video except I do infact delete the file everytime I want to change something. I run echo >> file.ml (ocaml BTW) every time I need to edit something.
It's a more functional way to program. Having random, nonrecursive access to a character in a file, like having access to an element in an array introduces state into the writing of my program
You forgot to say:
Hopefully this video was suitable.
Subbed, this was very good thank you.
I trust this man because he's wearing a PhD jacket
Thanks for this, very helpful video
Emacs is decades old...how it uses tree-sitter?
I thought this video is about how to do a job where you clean and water the trees when the tree owner isn't home.
3:38 oof. I didn't come here to be roasted 😭
I wish it was easier to create own custom parsers and stuff, so it’s as easy to add tree-sitter syntax highlights than it was with old Vimscript.
I think I understood it. So treesitter is an interpreter that serves language protocols?
Great video Teej!
That is as close to art as it can be
couldnt it be sql or a subset of it? everybody knows sql but what the hell is that query syntax
How do you open the query editor?
How do you do a slideshow in nvim?
It’s a CLI tool called lookatme
correct! it's in the description
Dude you're on a roll