More #neovim spring cleaning 🧹 Replaced the trusty vim-commentary with Comment.nvim. It's context aware and can use #treesitter to determine the correct commentstring for injected languages. 👍 https://github.com/numToStr/Comment.nvim
Difftastic is a CLI diff tool that compares files based on their syntax, not line-by-line. Difftastic produces accurate diffs that are easier for humans to read.
It supports many languages and is compatible with Git.
#Neovim in #Debian is finally updated past the 0.7.2 release (up to 0.9.4) 🎉
It's been a long time coming, and it's just in experimental for now.
The long pole, aside from ENOTIME, was introducing the #treesitter ecosystem to Debian. That took a bit longer than I was expecting, and I'm still not happy with how it looks. I've started poking around at debhelper tooling to simplify this, since the packaging is pretty repetitive for treesitter grammars.
Just started to write a blog post about my #neovim and #treesitter adventures and figured out even this works: Sql inside #Rust inside Markdown. And the highlighting is still correct.
Last time I laid out the case for why we chose to embrace TextMate-style scope names, even in newer Tree-sitter grammars. I set a difficult challenge for Pulsar: make it so that a Tree-sitter grammar can do anything a TextMate grammar can do.
Today, I'd like to show you the specific problems that we had to solve in order to pull that off.
#NeoVim update. The discovery of registers has made me very happy. Macros are saving me a lot of time!
I'm slowly improving my speed with movements. It's also forcing me to address some bad typing habits of mine.
#AsciiDoc support using vim-asciidoctor is better than the built-in syntax highlighting, but it's still mediocre and breaks. In an ideal world there would be a #Treesitter parser for it, but I don't know if I have the energy/skill to work on that.
Is anyone using the tree-sitter based C/C++ modes in Emacs 29 and working with codebases that use "weird" indentation styles? It seems like they only support "gnu, k&r, bsd and linux" - and none of those match what I'm up against, exactly.
Is there any benefit actually to using tree-sitter? I don't notice any obvious differences in syntax highlighting or anything...
@lambdageek I am planning to use tree-sitter for C++ as well, but my first attempts also failed due to different indentation from what I have configured for the standard C++ mode. In the meantime however I read somewhere that there are ways to adjust indentation rules for the tree-sitter modes, but I didn't find the time yet to investigate in more depth. #emacs#treesitter
#nvim regexplainer, the plugin which tells you what your #regex is doing, now has long-awaited support for lookbehind assertions, thanks to the fixes in the upstream #treeSitter parser
Many people seem to agree that part of what makes #git (& #dvcs in general) so difficult to get a really effective handle on is that applying patches is a lot like working with pre-processor macros (ie #define in #C), and that there oughta be a more well-bounded, lexically concise means of code collaboration to establish. But the only work I've seen in this direction is Arun Isaac's tree-diff[1]. #TreeSitter[2] seems like a tool that can greatly ease experimentation in this direction, but what other work has been done on this problem?