2021/12/31/using_nvim_after_three_years/
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 27
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Using Neovim for Three Years - jdhao's blog
I started using Neovim (nvim for short) about three years ago, in Sep. 2018. At that time, nvim had just released version 0.3.1. Over the years, I have been an adamant nvim user, constantly learning new knowledge, and sharing tips, tricks and interesting plugins in my blog posts.
https://jdhao.github.io/2021/12/31/using_nvim_after_three_years/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the linked Neovim article and inspect the repository's Hugo content structure first. The issue does not state what should be changed or identify a file, so clarify the intended contribution and acceptance criteria before starting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- neovim
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100