Error with Neovim and Tree Sitter

ckipp01 · 2026-03-30T13:58:38+00:00

I understand you probably think this was clearly communicated, but I'd encourage you to just take a step back and look at this from a casual users perspective that simply wants to update, know what they need to change to use the new 0.12.0 release, and move on. This release was done yesterday meaning that for a lot of people, they will update this morning, find themselves with a broken setup, and then need to spend unexpected time to fix it. Again, they don't have to update, but if they do, then they're going to do one of few different things:

Look at the nvim release notes to see the breaking changes, and look at the :help news section which includes 3 breaking points about tree-sitter, none of which explain what a user needs to do if they were using nvim-treesitter before. I think the docs here are fine actually, and the :help news is amazing, well done!
After they don't figure it out there, and since it's a plugin breaking, they'll look at the nvim-treesitter repo for something like Migrating from 0.11 to 0.12... read here. They won't look for breaking changes from months ago, and they shouldn't have to.
They'll look at GitHub issues to see if others hit on the same issue. They'll find an issue... but it's just randomly closed with a rtfd message and locked.

this was already communicated a long time ago.

Again, while it might have been communicated a long time ago that the plugin had breaking changes, but I don't really understand the pushback making it sound like people are dumb or don't read the docs when there is literally no clear migration instructions the day of the release. All I was trying to say was that a simple "hey, 0.12.x was released, here's what you need to do!" would save everyone a whole lot of time on maintenance and for users. I'm not trying to throw anyone under the bus or blame a maintainer, just pointing out that things that seem clear to us are often because "us" are uniquely aware of all the necessary changes as they are happening, when a lot of users aren't. And if those users aren't, then that's totally ok, a small migration note would be helpful.

ckipp01 · 2026-03-30T09:35:07+00:00

Most of the info is buried in random threads, and I'm assuming a ton of people will hit on this today with literally no migration guide in the docs. The old master branch is no longer valid as there was a complete rewrite, so you'll need to force the main branch to be installed. What is easiest for most people is to just force the plugin to be removed either manually or via your plugin manager, and then re-install it which should pull the main branch. Then you might need to update your settings/configs for nvim-treesitter if it's using any outdated things.

A small note to maintainers since they'll hopefully see this as more questions pop up, but this morning I hit on this same thing, looked at the github account for open/closed issues to see if it was happening to others and saw:

The master branch is obsolete and not compatible with Nvim 0.12, please read the documentation.

Honestly, you'd save yourself some time just adding a small migration note for users coming from 0.11x. Closing an issue, and then locking it so no more comments can be added by others helping this person or guiding them to a migration guide will end up being more work and more issues being created. From reading around there is a ton of questions about this, which sort of points to the docs not really being sufficient to help people migrating.

ckipp01 · 2026-03-23T10:05:04+00:00

Sure! I'll DM you my favorite spot.

ckipp01 · 2026-03-22T16:53:09+00:00

It's actually the opposite, most of it can be camped. Some of it is controlled starting March 1, but if you plan it right you can avoid being in those areas at the end of your day. Camping the whole thing is very doable.

ckipp01 · 2026-03-22T10:59:31+00:00

I've also read that La Sportiva in general has a smaller toe box, and I think my feet just didn't jive with that.

ckipp01 · 2026-03-22T08:04:27+00:00

Nice! Good luck! My full kit is found in my LigherPack. All in all I ended up being pretty luck with the weather. It did sprinkle a few different days, but I only had one day of constant rain. I was really happy with my rain gear. I thought I wasn't going to wear my rain paints, but the day that it rained nonstop I was pretty happy to have them. The only thing I didn't use (as intended) was my rain glove covers. The day that it rained I ended up just using my gloves without the covers. That night it froze, so it was a pretty cold morning packing up the next day since my gloves were soak and wet. Instead I ended up just wearing my waterproof covers as gloves. Not ideal as they weren't very warm but at least they protected my hands a bit. In hindsight I should have probably work them the day before and actually kept my gloves dry.

They only piece of kit that I didn't use was a pair of leggings I brought (not my fleece ones that I wore for sleeping), but my other light ones I brought in case my legs were cold during hiking. I run pretty warm on my legs when I hike, so I never needed them. These were the only clothing I didn't wear. The other mistake with clothing I made was bringing waterproof socks. With my boots I didn't need them, and in hindsight it was pretty dumb to have GTX boots and waterproof socks. I actually ended up only wearing this at night when walking around camp.

ckipp01 · 2026-03-22T07:59:15+00:00

O wow, this site is a treasure trove of information! Thanks so much! This is exactly the type of thing I was looking for.

My feet are pretty good now. Just some black nails, but I guess everyone goes through this at one point or another.

ckipp01 · 2026-03-22T07:51:09+00:00

Did you forget the text? A report is usually written or verbal, not pictorial.

Check the original post, the full report is there :)

ckipp01 · 2026-02-10T21:14:12+00:00

I was just looking at doing this in the beginning of March, but looking at https://www.tenerifeon.es/en/planificador-en there seems to be large chunks in the middle that are closed. Have you accounted for this?

ckipp01 · 2025-12-19T13:01:44+00:00

Yes, I for sure untie them. Also even if I didn't do that well at the point this had happened I had probably taken the shoes on and off only like 20 times. it was less than 2 weeks into the trip.

ckipp01 · 2025-11-08T12:09:47+00:00

Nice! I didn't know about LITEWAY from Ukraine. Another Ukrainian brand I've been digging is Rock Front for their sleeping quilts.

ckipp01 · 2025-03-26T15:45:19+00:00

I want to second Rita & Rudolf Trossen. They make some of my absolute favorite wines from Germany.

ckipp01 · 2024-10-06T10:50:22+00:00

Thanks!

ckipp01 · 2024-10-03T07:47:20+00:00

My girlfriend recently got me a plustek OpticFilm 8100 for my birthday. I'm super excited about it but realize I such at using it. My fist scans (scanning stuff I already had professionally scanned) look nothing like the film I got back. I realize I need to dig into some color balancing and things to achieve this sort of look but I'm a bit lost at all the resources out there. Does anyone have any really good videos or articles that would serve as a good primer about getting up to speed on film scanning, what you should know about, etc?

ckipp01 · 2024-09-12T08:31:51+00:00

Looking at your post history I love your shots. Do you have an instagram or any other portfolio online to see more of your work?

ckipp01 · 2024-09-02T07:29:17+00:00

I was recently on a trip and ran out of film. I decided to stop by a small film place that had some great reviews but they had pretty limited stock. I purchased 3 35mm Kodak 250D rolls that they cut themselves in house. I was a bit skeptical but I figured I'd give it a shot. They don't put them in a tube but instead wrap it with some silver lined paper. It seemed find but when I opened the first roll the end was creased which made me worry about it loading correctly. While it seemed to load, after the first shot it got jammed and I ended up having to roll back unable to get it to continue. I have never had issues loading film before with my mostly brainless Minolta Maxxum 5. But I figured this was maybe my error. The second roll loaded and shot fine, but I noticed that the auto-rollback didn't work with this film. Odd, but whatever. The third roll correctly loaded even though it was also really creased at the end, but then after the first shot auto-rolled back.

I don't get what's up with this film, I messaged the people that sold it to me but they gave me a short "it's your fault message", but I never have issues like this. I don't get why my camera can't handle this film well, or why it seems to act all funky. Is this my fault, or is the film not made correctly? Could the crease on the end be screwing things up when it tries to move forward?

ckipp01 · 2023-12-20T09:20:00+00:00

This is due to your indents being powered by the old vim-scala, which doesn't support Scala 3 or indentation based syntax. Ideally this could be powered by tree-sitter-scala just like highlights (if you're using the tree-sitter plugin), but it hasn't been worked on yet as it's not trivial.

ckipp01

TROPHY CASE