Evgeni Chasnovski

mini.diff config for jujutsu · echasnovski mini.nvim · Discussion #1783 Sharing in case someone finds it useful. Should work with multiple repos/workspaces. Doesn't have hunks since those don't make sense with jj. Uses --ignore-working-copy so it should pollute your op...

Take a look at this 'mini.diff' config: github.com/echasnovski/...

There are plans to make this setup more streamlined, but no time frame yet.

But judging by the video, it is a direct Insert mode mapping for `jk` somewhere. The cursor slightly "lags" after pressing `j` when typing slowly. It means that Neovim waits for the next key to decide if the letter should be inserted or is it a part of a mapping.

It is a 'better-escape' type of plugin. This showcases its intended usage: quickly typing some two letters (usually `jk`) exits into Normal mode.
For some people it is easier than `<Esc>`, but for me it feels too intrusive.

neovim's built-in "treesitter support" is a cool feature that has been around for a while now. i didn't found many resources that explain what is, so i wrote something

vonheikemen.github.io/learn-nvim/f...

#neovim

Then look at Neovim issues to see what makes *you* want to fix it.

But note that not only Lua fix/feature is a valuable contribution. Improving documentation (better wording or typo fix) or Lua types are very welcome.

There is also C part of thr codebase, but I know very little about it.

Try to first get comfortable with Lua and Neovim. I think the best "exercise" here is to write your own statusline. Not for other people to use it, but only for own config.

Writing the plugin that solves some practical issue is a good second step. It can be for a language or tool, for example.

I have been making appeals regularly, but there is no effect currently.

If anyone has a more direct line of communication with Reddit support/admins outside of regular appeals or Redditor help center, I'd highly appreciate if they take a look at the account status. Thanks 🙏

PSA: my Reddit account (same as Bluesky handle) has been suspended for 11 days now. All its past content (mostly #neovim posts + comments) is currently hidden by Reddit filters.

It was due to a false positive inauthentic activity detection. I reset the password, but account is still shadow banned.

Neovim vs Emacs | Roundtable w/ TJ DeVries, DistroTube, Greg Anders & Joshua Blais
(Video in 1st comment)

It is a more organized way of modifying 'runtimepath' *plus* executing necessary 'plugin/' scripts, yes. Like, it will also add plugin's 'after/' directory to 'rtp' if needed.

Thanks for trusting 'mini.nvim'! There are still many modules for you to try :)

I've read the post earlier today and it (re-)made me aware about the 'inccommand=split'. I somehow didn't remember it. So thanks for spreading the knowledge!

Hm, that's an interesting one to cause issues. But yeah, I get it (after reading the full thread) why you experienced it. 'mini.statusline' does assume that it is the one responsible for setting 'statusline' option.

I don't think there will be a long term damage here because it is meant as an automation tool. If users want to manage fully manually, this should be still possible with 'pack/*' packages and git submodules. Like I also used to do before 'mini.deps' :)

Indeed, one of the optimistic end goals is to have a built-in plugin manager that can respect data about plugins that they themselves provide: install/update dependencies, run hooks on install/update/delete, etc.

Right now it requires manually adding dependencies and setting up hooks.

Would you mind sharing what was the issue? Was it a dedicated breaking change or something unintentional?

AFAIK, there is a planned out of the box tree-sitter installation: github.com/neovim/neovi...

There is some misunderstanding here. `:packadd` doesn't modify 'packpath'; it searches in its directories and adds first match to 'runtimepath' (`:h pack-add`). So it is already a built-in way to properly modify 'runtimepath'.

The reason is mostly to reuse existing "infrastructure" of packages and not re-invent how plugins are sourced.

'packpath' is not affected. It reuses the default suggested path that is already present there.

`vim.pack` doesn't require user to know 'start' vs 'opt' lore. Just `vim.pack.add()`.

Yeah, it would require each 'opt/' subdirectory as a separate Git repo. So it is a matter of how to package the plugin.

If there is an automatic dependency resolution in the future, all of them can be added as dependencies to some dummy plugin.

It was a long road to get here, but we made it 🎉
Thanks @neovim.io core team for allowing me to do this!

There are still a lot of things to do, but we'll approach them one small step at a time.

Yes, backward compatibility with at least two previous stable Neovim versions is a goal. Only recently stopped supporting 0.8.

There might be limited support of some features, but only if it is impossible/hard to do on older versions.

Glad that this effort has its audience :)

After skimming some sections, it is very nicely written. I liked that you mentioned built-in packages instead of locking users to a single plugin manager.

And thanks for mentioning 'mini.nvim'🙏

As far as I know, this is only a "money in exchange for a spot on the web site". They have no input into the decisions and development in general. So not *that* bad.

While writing my prompt from scratch (as one does), decided to also try and have Neovim (#neovim) with 'mini.pick' be my CLI fuzzy finder. It was not as complicated as I feared at first. Definitely has its shortcomings, but works okay.

Here is how the result looks:

Switching from Zsh to Nushell brings back memories of switching from Vim to Neovim. Nu language feels nicer for config and customized tweaking compared to Bash, in the same way as Lua is to Vimscript.

I've been interested to try Nushell for some time now. Several weeks ago decided to give it a try.

To me it looks good enough to daily drive, but only if you are comfortable adjusting the setup after new releases (as both language and shell behavior is not quite stable yet).

LazyVim uses `gsa`/`gsd`/etc instead of `sa`/`sd`/etc. I personally find it too verbose.
Instead I'd suggest using different key for jumping. My preferred choice is <CR>, but other good candidates are <Tab> and maybe even `sj`.

Thanks for kind words!

To be fair, there most certainly are others. I *think* 'j-hui/fidget.nvim' should show this (at least there is something Rust-like in the demo). But I do like some design choices of 'mini.notify' better.

Yes, but for closing brackets and quotes:
github.com/echasnovski/...

All of that Vimscript is in runtime files (like filetype plugins, syntax files, color schemes) and tests. The Neovim source is overwhelmingly C and Lua.

So don't let your dreams be dreams :)