80 lines
4.3 KiB
YAML
80 lines
4.3 KiB
YAML
uuid:
|
|
- value: ba4ccfb6-f00d-4fb2-8519-aa43356218f6
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:57+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: 'Why I work in Neovim'
|
|
created:
|
|
- value: '2022-08-25T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:57+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2022/08/25/why-i-work-in-neovim
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>Over a year ago, I posted that I was <a href="/blog/going-full-vim">switching to using Neovim full-time</a> for my development work.</p>
|
|
|
|
<p>I'd used Vim one file at a time on remote servers, and added Vim plugins in other IDEs and editors, so I was already familiar with a lot of the key bindings and motions before I decided to use it full-time.</p>
|
|
|
|
<p>Still, it was tough to begin with, but once I'd learned how to configure Neovim, I also learned that being able to customise and extend it as much as you need to is one of its main advantages compared to other IDEs and code editors.</p>
|
|
|
|
<p>TJ DeVries - a Neovim core team member - has recently coined the term "PDE" (a personalised development environment) which, for me, describes Neovim perfectly.</p>
|
|
|
|
<p>Currently, I have a fuzzy-finder to quickly open files (as well as many other things), an LSP client to add code intelesense, auto-completion, refactoring tools, custom snippets, and very recently, a database client and a HTTP client.</p>
|
|
|
|
<p>Just as important to me, I've found a growing community of other Neovim users who stream on Twitch, post YouTube videos, write blog posts, or publish their dotfiles for others to see and reference.</p>
|
|
|
|
<p>I've learned Lua. Not just for my own Neovim configuration, but I recently wrote and open-sourced my own simple plugin.</p>
|
|
|
|
<p>Like Git, I enjoy and prefer using tools that I can configure and adapt to my workflow.</p>
|
|
|
|
<p>Given Neovim's flexibility and configurability, its expanding feature set both in core and community plugins, and the growing community, I think that Neovim is going to be something that I continue to use and adapt for a long time.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>Over a year ago, I posted that I was <a href="/blog/going-full-vim">switching to using Neovim full-time</a> for my development work.</p>
|
|
|
|
<p>I'd used Vim one file at a time on remote servers, and added Vim plugins in other IDEs and editors, so I was already familiar with a lot of the key bindings and motions before I decided to use it full-time.</p>
|
|
|
|
<p>Still, it was tough to begin with, but once I'd learned how to configure Neovim, I also learned that being able to customise and extend it as much as you need to is one of its main advantages compared to other IDEs and code editors.</p>
|
|
|
|
<p>TJ DeVries - a Neovim core team member - has recently coined the term "PDE" (a personalised development environment) which, for me, describes Neovim perfectly.</p>
|
|
|
|
<p>Currently, I have a fuzzy-finder to quickly open files (as well as many other things), an LSP client to add code intelesense, auto-completion, refactoring tools, custom snippets, and very recently, a database client and a HTTP client.</p>
|
|
|
|
<p>Just as important to me, I've found a growing community of other Neovim users who stream on Twitch, post YouTube videos, write blog posts, or publish their dotfiles for others to see and reference.</p>
|
|
|
|
<p>I've learned Lua. Not just for my own Neovim configuration, but I recently wrote and open-sourced my own simple plugin.</p>
|
|
|
|
<p>Like Git, I enjoy and prefer using tools that I can configure and adapt to my workflow.</p>
|
|
|
|
<p>Given Neovim's flexibility and configurability, its expanding feature set both in core and community plugins, and the growing community, I think that Neovim is going to be something that I continue to use and adapt for a long time.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|