mastodon.ie

Florian PircherI’ve published a <a href="https://typo.social/tags/TreeSitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#TreeSitter</a> grammar for the Property List format: <a href="https://github.com/Formkunft/tree-sitter-property-list" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Formkunft/tree-sitter-property-list</a>Useful for syntax highlighting, indentation, or any other structural analysis of plist files.

snamellitRecently with verion 0.25 the treesitter library changed ABI version to 15. Newer parsers will complain about a version mismatch if the installed library used by emacs is lower than this version. This ABI version was introduced in the 0.25 branch of treesitter. The best course of action till lib treesitter is updated is to pin the version of the parser to the last version supporting ABI 14. With the new ABI 15 version, parsers are required to provide a ~treesitter.json~ file with additional metadata which can be used as proxy to find a version which still supports ABI-14, i.e. the commit before that. A lot of the parsers are provided by the treesitter project as sub repos, and they follow the same version convention as the library, selecting the last tag before the 0.25 tag is a good way to find a compatible version. This branch can be added after the repo url in the ~treesit-language-source-alist~ variable. Note that if you use ~treesit-auto-install-all~ to get it over with, you have to probably restart your emacs as treesit-auto apparently caches the value during iniitialisation and changes are not picked up. <a class="hashtag" href="https://social.snamellit.com/tag/emacs" rel="nofollow noopener" target="_blank">#emacs</a> <a class="hashtag" href="https://social.snamellit.com/tag/treesitter" rel="nofollow noopener" target="_blank">#treesitter</a>

andie :oh_no_bubble:I made a small NeoVim Plugin and custom Tree-Sitter parser to enhance the journalling experience with Fern Log files. It supports various syntax and entry highlights, header folds, and a few keybindings for toggling statuses and folds quickly (for now). Blog post introducing it: <a href="https://bugwhisperer.dev/blog/fern-neovim-plugin-treesitter-parser/" rel="nofollow noopener" target="_blank">https://bugwhisperer.dev/blog/fern-neovim-plugin-treesitter-parser/</a> Code repo: <a href="https://github.com/bugwhisperer418/fern.nvim" rel="nofollow noopener" target="_blank">https://github.com/bugwhisperer418/fern.nvim</a> Excited to keep improving it! :celsilvercrystalheart: I welcome any feedback or suggestions. Thank yooou!! <a href="https://blahaj.zone/tags/neovim" rel="nofollow noopener" target="_blank">#neovim</a> <a href="https://blahaj.zone/tags/treesitter" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://blahaj.zone/tags/journalling" rel="nofollow noopener" target="_blank">#journalling</a>

Shae ErissonDoes anyone know of other tools that use <a href="https://recurse.social/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> to do something nifty?I'm a recent convert to both difftastic[1] and combobulate[2], what else is in that space?There must be more awesome uses of concrete syntax trees?[1] <a href="https://www.wilfred.me.uk/blog/2022/09/06/difftastic-the-fantastic-diff/" rel="nofollow noopener" translate="no" target="_blank">https://www.wilfred.me.uk/blog/2022/09/06/difftastic-the-fantastic-diff/</a>[2] <a href="https://www.masteringemacs.org/article/combobulate-structured-movement-editing-treesitter" rel="nofollow noopener" translate="no" target="_blank">https://www.masteringemacs.org/article/combobulate-structured-movement-editing-treesitter</a>

Antonin Delpeuch<a href="https://mamot.fr/tags/Mergiraf" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mergiraf</a> 0.7 is released 🪂 🦒! It includes quite a few bug fixes and UX improvements, so it's worth upgrading :)<a href="https://codeberg.org/mergiraf/mergiraf/releases/tag/v0.7.0" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/mergiraf/mergiraf/releases/tag/v0.7.0</a> <a href="https://mamot.fr/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> <a href="https://mamot.fr/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://mamot.fr/tags/codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#codeberg</a> <a href="https://mamot.fr/tags/jujutsu" class="mention hashtag" rel="nofollow noopener" target="_blank">#jujutsu</a>

XavierI finally got around to wrapping up and publishing a first version of my <a href="https://sunny.garden/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a> crate ts-typed-ast. It's a crate inspired by Rowan that automatically generates a typed AST from a tree-sitter grammar. You can find it here: <a href="https://crates.io/crates/ts-typed-ast" rel="nofollow noopener" translate="no" target="_blank">https://crates.io/crates/ts-typed-ast</a>It works similarly to Rowan and Swift's libsyntax. tree-sitter provides the green nodes, while this crate generates the red nodes.I've used it a few times already, to prototype various toy programming languages. You write a grammar in tree-sitter, and then either evaluate the ts-typed-ast tree directly, or convert it to some other IR.Using tree-sitter as the parser generator for a toy project is pretty nice. You get a powerful, declarative way to create a parser, and at the same time you benefit from the whole tree-sitter ecosystem. Things like incremental parsing, syntax highlighting, structural editing, and formatting with Topiary.Main downside is that tree-sitter does not (yet) offer good error reporting and recovery, so when parsing fails it's often in dramatic, unhelpful ways. Not a big issue for experimenting, which is what this crate is for. Production-ready languages probably need bespoke parsers anyway.<a href="https://sunny.garden/tags/parser" class="mention hashtag" rel="nofollow noopener" target="_blank">#parser</a> <a href="https://sunny.garden/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://sunny.garden/tags/pl" class="mention hashtag" rel="nofollow noopener" target="_blank">#pl</a> <a href="https://sunny.garden/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a>

Dale EmeryI’ve looked briefly at <a href="https://mstdn.social/tags/Treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#Treesitter</a> queries a few times, and bailed out each time because at a glance it looks more complicated than I was motivated to push through.Turns out they’re not very complicated. A little weird… until you realize they’re structured similarly to LISP things.Once I grokked that, it didn’t take long to undersand the syntax. <a href="https://tree-sitter.github.io/tree-sitter/using-parsers/queries/index.html" rel="nofollow noopener" translate="no" target="_blank">https://tree-sitter.github.io/tree-sitter/using-parsers/queries/index.html</a>Now I’ll see whether I want to do something with them beyond what comes stock in <a href="https://mstdn.social/tags/neovim" class="mention hashtag" rel="nofollow noopener" target="_blank">#neovim</a> and the nvim-treesitter plugin.

Patrick Wu :neocat_flag_bi:First time writing tree-sitter definitions, so any feedback would be appreciated... This is a tree-sitter definition for OpenSIPS configurations: <a href="https://code.wedotstud.io/patrick/tree-sitter-opensips" rel="nofollow noopener" translate="no" target="_blank">https://code.wedotstud.io/patrick/tree-sitter-opensips</a><a href="https://o0o.social/tags/opensips" class="mention hashtag" rel="nofollow noopener" target="_blank">#opensips</a> <a href="https://o0o.social/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://o0o.social/tags/neovim" class="mention hashtag" rel="nofollow noopener" target="_blank">#neovim</a> <a href="https://o0o.social/tags/voip" class="mention hashtag" rel="nofollow noopener" target="_blank">#voip</a>

robinm<a href="https://mamot.fr/@mdk" class="u-url mention" rel="nofollow noopener" target="_blank">@mdk</a> I'm using [mergiraf](mergiraf.org/) since about 2 months. It's has much fewer false positive than the default line based merge algorithm, but a bit more false negative. It does use tree sitter to compare and merge, a bit like what [difftastic](difftastic.wilfred.me.uk/) does for diffing files.<a href="https://fosstodon.org/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://fosstodon.org/tags/mergiraf" class="mention hashtag" rel="nofollow noopener" target="_blank">#mergiraf</a> <a href="https://fosstodon.org/tags/difftastic" class="mention hashtag" rel="nofollow noopener" target="_blank">#difftastic</a>

Bozhidar Batsov (a.k.a. Bug)With <a href="https://hachyderm.io/tags/Emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Emacs</a> 30 recently released I finally felt that the time has come to go all in on <a href="https://hachyderm.io/tags/TreeSitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#TreeSitter</a>. (I am rarely an early adopter of anything these days) Over the weekend I had a lot of fun playing with TreeSitter and I started a prototype of an <a href="https://hachyderm.io/tags/OCaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#OCaml</a> major mode using it <a href="https://github.com/bbatsov/neocaml" rel="nofollow noopener" translate="no" target="_blank">https://github.com/bbatsov/neocaml</a>

SallyABLView from tonight's sunset walk in Canberra. <a href="https://aus.social/tags/Sunset" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sunset</a> <a href="https://aus.social/tags/TreetrunkTuesday" class="mention hashtag" rel="nofollow noopener" target="_blank">#TreetrunkTuesday</a> <a href="https://aus.social/tags/Nature" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nature</a> <a href="https://aus.social/tags/Photography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Photography</a> <a href="https://aus.social/tags/PhotoOfTheDay" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhotoOfTheDay</a> <a href="https://aus.social/tags/Bushland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bushland</a> <a href="https://aus.social/tags/Landscape" class="mention hashtag" rel="nofollow noopener" target="_blank">#Landscape</a> <a href="https://aus.social/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://fuzzies.wtf/@altbot" class="u-url mention" rel="nofollow noopener" target="_blank">@altbot</a>

Programming Languages DelftMaster thesis by Hendy Liang: "Property-Based ASTs: Enabling Language Parametricity in Refactoring Tools""By leveraging Tree-Sitter, a parser generator that creates parsers that produce generic, property-based ASTs, this research adapts Renaissance, an existing industrial refactoring tool, to support multi-language extensibility with minimal additional effort."<a href="https://repository.tudelft.nl/record/uuid:6e143a35-32b8-4f7e-928e-52057ea57566" rel="nofollow noopener" translate="no" target="_blank">https://repository.tudelft.nl/record/uuid:6e143a35-32b8-4f7e-928e-52057ea57566</a><a href="https://akademienl.social/tags/LanguageParametricity" class="mention hashtag" rel="nofollow noopener" target="_blank">#LanguageParametricity</a> <a href="https://akademienl.social/tags/refactoring" class="mention hashtag" rel="nofollow noopener" target="_blank">#refactoring</a> <a href="https://akademienl.social/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://akademienl.social/tags/thesis" class="mention hashtag" rel="nofollow noopener" target="_blank">#thesis</a>

petrisch<a href="https://mastodon.social/@gbraad" class="u-url mention" rel="nofollow noopener" target="_blank">@gbraad</a> sounds like <a href="https://swiss.social/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> magic. Really don't know why nobody wants that in v$code anymore.

Antonin DelpeuchI am looking into starting an organization for collective maintenance of <a href="https://mamot.fr/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> grammars, in the spirit of <a href="https://fosstodon.org/@jazzband" class="u-url mention" rel="nofollow noopener" target="_blank">@jazzband</a>. Would anyone be interested in joining? If anyone has insights about how <a href="https://mamot.fr/tags/jazzband" class="mention hashtag" rel="nofollow noopener" target="_blank">#jazzband</a> (or similar) has been doing, I am also keen to learn more.

aemogiei've only ever seen proper structural editing with lisps. in emacs you have things like paredit. and i get it, parsing lisp is trivial, text wrapped in pairs of parantheses are your parse nodes. but we have treesitter. we can do so much more.i could just write code and not care about syntax at all. i shouldn't ever have to fight it. and my editor should be a parse tree editor, not a text editor. text just isn't my interface most of the time. if i'm writing prose, maybe. but usually, i'm not.when i hit <code>w</code> in vim style binds often mean to go to the next sibling node. but i'm having to spam that and some amount of <code>h</code> or <code>l</code> to get to where i want to go. when writing code i don't think in words or characters. when i hit <code>j</code> i often mean to go to the next statement or expression.<a href="https://tech.lgbt/tags/lisp" class="mention hashtag" rel="nofollow noopener" target="_blank">#lisp</a> <a href="https://tech.lgbt/tags/paredit" class="mention hashtag" rel="nofollow noopener" target="_blank">#paredit</a> <a href="https://tech.lgbt/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://tech.lgbt/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#vim</a> <a href="https://tech.lgbt/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a>

aemogieand most of these modern text editors have the parse trees, for syntax highlighting. treesitter supports how many languages, now?why dont they leverage the already existing infrastructure? no extra dependencies to be added or anything. just use what you already bring in, but better.theres already selection that leverages treesitter in most editors. im not sure of neovim, but in helix it's built-in with alt-o, and in emacs you can use the expreg package (i think that's what it's called). but why is that all we have? and it's in addition to the existing selection, not in-place of it. why don't we have similar things for the other editing ui, like navigation, deletion, copy, cut, etc.i think i know, and i believe it's because selection is the only thing that's been way too painful with traditional line based or word based selection. it's imprecise, cumbersome, and just overall painful. but everything else, it's just okay enough that people are fine with it.<a href="https://tech.lgbt/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> <a href="https://tech.lgbt/tags/structuralediting" class="mention hashtag" rel="nofollow noopener" target="_blank">#structuralediting</a>

The Last Psion | Alex<a href="https://oldbytes.space/tags/Pascal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pascal</a> autocomplete and snippets in <a href="https://oldbytes.space/tags/NeoVim" class="mention hashtag" rel="nofollow noopener" target="_blank">#NeoVim</a>? Don't mind if I do!This is thanks to blink-cmp, using the snippets JSON file from the Pascal plugin for <a href="https://oldbytes.space/tags/VSCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#VSCode</a>, plus the pasls <a href="https://oldbytes.space/tags/LSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#LSP</a> and <a href="https://oldbytes.space/tags/Treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#Treesitter</a>.The LSP is incomplete, but it's better than nothing.<a href="https://oldbytes.space/tags/LazyVim" class="mention hashtag" rel="nofollow noopener" target="_blank">#LazyVim</a> <a href="https://oldbytes.space/tags/ObjecPascal" class="mention hashtag" rel="nofollow noopener" target="_blank">#ObjecPascal</a> <a href="https://oldbytes.space/tags/FreePascal" class="mention hashtag" rel="nofollow noopener" target="_blank">#FreePascal</a>

Space HoboEDIT: I am not looking to set up TreeSitter on neovim. I have that working fine, but only for bog standard 2024 syntax like awk or C or Makefiles. I want a *new* syntax definition for an old assembler that targets 12-bit minicomputers from the 1960s.Hey, are there any <a href="https://teh.entar.net/tags/NeoVim" class="mention hashtag" rel="nofollow noopener" target="_blank">#NeoVim</a> nerds here who can help folks with slightly older versions? I have a goal of "don't make my vi installation a full-time job" and I'm doing a lot of <a href="https://teh.entar.net/tags/PDP8" class="mention hashtag" rel="nofollow noopener" target="_blank">#PDP8</a> assembly in PAL. I can supply a <a href="https://teh.entar.net/tags/Kate" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kate</a> syntax file that does well enough (I use it for <a href="https://teh.entar.net/tags/pandoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#pandoc</a>), but I need a <a href="https://teh.entar.net/tags/TreeSitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#TreeSitter</a> syntax wotsit that I can just Install without having to upgrade NeoVim or TreeSitter past what's in Debian (this is non-negotiable: anything else has always become a full-time job for me).All the TreeSitter tutorials say to use an init command that doesn't exist in my copy, and I lost patience right then. The architecture makes it seem like this is only a pain for setting up a new project, but I don't have the attention to devote to this. I'd also like it if PAL8 syntax made it into whatever mainstream syntax repositories TS grabs from.

Antonin DelpeuchNew blog post: <a href="https://mergiraf.org" rel="nofollow noopener" translate="no" target="_blank">https://mergiraf.org</a>, a syntax-aware merge driver for <a href="https://mamot.fr/tags/Git" class="mention hashtag" rel="nofollow noopener" target="_blank">#Git</a>.Supports <a href="https://mamot.fr/tags/Java" class="mention hashtag" rel="nofollow noopener" target="_blank">#Java</a>, <a href="https://mamot.fr/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#Rust</a>, <a href="https://mamot.fr/tags/Golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#Golang</a>, <a href="https://mamot.fr/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>, <a href="https://mamot.fr/tags/cpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpp</a>, <a href="https://mamot.fr/tags/csharp" class="mention hashtag" rel="nofollow noopener" target="_blank">#csharp</a>, <a href="https://mamot.fr/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a>, <a href="https://mamot.fr/tags/json" class="mention hashtag" rel="nofollow noopener" target="_blank">#json</a>, <a href="https://mamot.fr/tags/yaml" class="mention hashtag" rel="nofollow noopener" target="_blank">#yaml</a> and <a href="https://mamot.fr/tags/xml" class="mention hashtag" rel="nofollow noopener" target="_blank">#xml</a> so far, and it's quite easy to add support for more thanks to <a href="https://mamot.fr/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a>.<a href="https://antonin.delpeuch.eu/posts/mergiraf-a-syntax-aware-merge-driver-for-git/" rel="nofollow noopener" translate="no" target="_blank">https://antonin.delpeuch.eu/posts/mergiraf-a-syntax-aware-merge-driver-for-git/</a>Get it on <a href="https://mamot.fr/tags/Codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#Codeberg</a>: <a href="https://codeberg.org/mergiraf/mergiraf" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/mergiraf/mergiraf</a>

Bharath M. PalavalliPfft, <a href="https://mastodon.sdf.org/tags/eglot" class="mention hashtag" rel="nofollow noopener" target="_blank">#eglot</a> broke again, does anyone have a simple way to set it up with <a href="https://mastodon.sdf.org/tags/treesitter" class="mention hashtag" rel="nofollow noopener" target="_blank">#treesitter</a> for <a href="https://mastodon.sdf.org/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a>? I just haven’t been able to figure out how to set it up without it breaking on me often. I mostly need it for R, Shell, Python, LaTeX, and Go.

Recent searches

Search options

Administered by:

Server stats:

#treesitter