rustic VS nvim-treesitter-context

I'm a huge fan of restic as well. My only complaint is performance and memory usage. I'm looking forward to being able to use Rustic: https://rustic.cli.rs/

Since this is HN, we also need to mention [Rustic](https://github.com/rustic-rs/rustic) which is better since it's in Rust.

For anyone just passing by, from the rustic website[0]:

> Stability: Currently our tools are in beta state and miss regression tests. It is not recommended to use them in production backups, yet.

[0]: https://rustic.cli.rs/

After a bit of refactoring, we are very proud to announce the first version of rustic_core, a library providing all functionality available in rustic, see https://www.reddit.com/r/rust/comments/12xs8h3/announcing_rustic_fast_encrypted_deduplicated/. In fact, rustic is now just a thin CLI wrapper around rustic_core.

There is support to extend a local repository using e.g. the par2 tool, see https://github.com/rustic-rs/rustic/blob/main/examples/par2.toml But for recovery, that would involve manually recovery of broken repository files.

Very cool! Sort of reminds me of treesitter-context. Any chance for compatibility? An example could be you either would disable context when something is pinned or somehow displace it other, depending on which is "on top" could be neat.

It's for context and navigation, not completions. So it wouldn't replace nvim-cmp. It probably doesn't replace anything you already have unless you are already using a winbar. It combines features of treesitter-context, symbols-outline, and a file navigator but in a different presentation.

Not quite the same thing, but arguably a better alternative : https://github.com/nvim-treesitter/nvim-treesitter-context

For 2: https://github.com/nvim-treesitter/nvim-treesitter-context

I really like nvim-treesitter-context as an alternative for 1.

nvim-treesitter-context implements "sticky scroll" where, depending on where your cursor is placed, the top lines of your window will be replaced by the otherwise offscreen lines that declare what function you're in (e.g function test(...), the line that begins the current class (e.g. public class Student implements Person {), the variable name of the current table (e.g. local planets = {), etc.

Very different in my eyes, but I love nvim-treesitter-context. Definitely another tool in helping the brain parse code -- I think of it as helping with long range context, whereas blockman helps me focus on local context and makes scoping relationships more subconciously available.

You are looking for this: https://github.com/nvim-treesitter/nvim-treesitter-context

I have seen https://github.com/nvim-treesitter/nvim-treesitter-context is recommended, and it works similar. But the way the context info are displayed in AstroNvim is much nicer