this-week-in-neovim-contents VS nvim-config

Moving to the actual action points: I think as a starter we could go with a couple of people requesting write access to phaazon/this-week-in-neovim-contents. The way I’ve been working is pretty simple:

Don't forget to add it to "This Week in Neovim". How to contribute -> https://github.com/phaazon/this-week-in-neovim-contents/blob/master/README.md

Hi /u/Thrashymakhus, please consider making a PR for this news in the upcoming This Week in Neovim edition! - How to Contribute to TWiN - Latest TWiN branch - Template Directory

Here is a link to a PR template for the update category.

Neat plugin! Would you mind if i open a PR to next week's https://github.com/phaazon/this-week-in-neovim-contents for you (or you can, as the author is looking for contributions from the community)?

Make a PR to "This Week In Neovim". Although it will probably be added anyways, this certainly helps maintaining newsletter.

Next time, feel free to open a PR to https://github.com/phaazon/this-week-in-neovim-contents/ so that it gets deployed to https://this-week-in-neovim.org. That would have had its place 100%.

Please feel free to send me the screenshots by opening a PR here, branch 2022-Jul-18 :)

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)