nvim-config VS mini.nvim

The detailed commit can be found here: https://github.com/jdhao/nvim-config/commit/3137850db67b1b45111656e8749b60eb936dfa7d

i'm using this configuration

How about giving a try with pre-configured setup. That’s how I started. It could be overwhelming to start from the scratch and you could make mistakes that is hard to track. I started with jdhao-nvim-config and learned stuff by looking at the configs. Removed stuff I don’t want and added stuff I need and customized things. Just a suggestion though. Good luck with your nvim journey 🤞

same issue here and found out the caveat is cmp-omni. Just remove it. check my commit: https://github.com/jdhao/nvim-config/commit/43c1615822eeeb29d8213ca117760476f9e9f4dc

Also my newest nvim config for nvim 0.8 can be found here: https://github.com/jdhao/nvim-config

easy customization. You can learn to do it in less than 5 mintues. See my conf here.

nah, I am probably more experienced in using nvim than you. Check my nvim notes here and my config here. People use nvim differently, I do not judge you, and you do not judge me. Your way of using nvim is definitely not the only true way 👌

The nvim binary build in Ubuntu 20.04 requires GLIBC 2.28, but libc.so on CentOS 7.4 only support up to GLIBC 2.17. I have downloaded the latest nightly nvim release for linux and run it on CentOS 7. It will not run.

Since I'm super new to all this, I'm using CoC for pretty much everything here, and my entire config based on https://github.com/jdhao/nvim-config (with some extra coc-config stuff; it got me this far, but no further)

This is essentially a tagline of mini.move.

Just as the others suggested, oil.nvim solves this outta the box. I freaking love it (here my config in case ya need it). Apparently also mini.files handles this by default

You mean backwards seeking text objects? You can get those with mini.ai https://github.com/echasnovski/mini.nvim/blob/main/readmes/mini-ai.md

I would like to offer you to join me in saying late greetings to this autumn with a release of mini.nvim version 0.10.0. It is mostly about introducing three (quite feature full, dare I say) modules and minor updates of existing ones.

Last night I cleaned up all the dead code in my config and realised that mini.nvim has to be the single best plugin that I've used. I have a couple of other favourites but this collection has been so consistently good that I wanted to give some thanks to the juggernaut that is u/echasnovski! Thanks for all the work you plugin authors and core maintainers put in to make this editor what it is <3

For example: I spent a lot of time configuring file tree plugins to have the same sorting as VS Code, tweaking their icons, etc. But then I realized I barely used the file explorer at all, and now I'm super happy with the minimal approach of mini.files. I had similar experiences with other plugins that were just adding "fluff" instead of the functionality I was looking for.

Around two weeks ago I've announced the release of mini.files - a file explorer module of mini.nvim with column view navigation and "edit text to manipulate file system" design. This resulted into a great feedback from the community, much of which turned into new features.

A mini.ai textobject specification that you can use standalone