Amaan Qureshi

> I have a huge code base with over 10K files. It includes minified JS files over 1 MB. Accidentally opening the JS file (or previewing them using telescope), neovim...

don't think he'll be back :disappointed: I can take over make soon

> @theHamsta fix did not work for me in the case of O/o continuation > > E.g. make a new `jsfile.js` and enter: > > ```js > /** > */...

> I'm still afflicted by this, even with an override to `queries/ecma/indents.scm`. My config might be a bit more complex, so I'm guessing there may be some more conflicts hidden...

#4524 rework indentation styling/format to be aligned with upstream, any plugins/modules that modified this will have to **use the new captures specified in the docs**

#5185 changed the upstream proto parser to a maintained one, just update the parser with `:TSUninstall proto` and `:TSInstall proto`

https://github.com/nvim-treesitter/nvim-treesitter/pull/5222 switched the upstream perl parser to a maintained one, just update the parser with :TSUninstall perl and :TSInstall perl

A way (or predicate) to check if it's a single line or not maybe, not sure if we have that

if you can attach gdb/lldb to neovim before opening that file you can generate a backtrace which will be very very helpful, just make sure you compile neovim w/ debug...

oh right, don't directly spawn it with lldb - instead launch nvim but don't open that file that crashes - then get the PID of neovim with ps aux |...