> For the complete documentation index, see [llms.txt](https://wiki.stojanow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.stojanow.com/tools/text-editor.md).

# Text Editor

[Vim](https://www.vim.org/) is my favourite text editor (I use [Neovim](https://github.com/neovim/neovim)). It has changed completely how I interact with text. Any editor that forces you to use a mouse is wasting your time.

Think of using Vim commands as composing sentences. Take a "verb"' `d` (delete) + a "subject" `w` (word) and a whole word is deleted. It's easier than pressing `ctrl + shift + right arrow + delete` in a normal editor.

Vim spoiled me to the point that I use vim-like movement to browse the web ([vimium](https://github.com/philc/vimium)).

My [config](https://github.com/psto/dotfiles/blob/master/init.vim) file and my [nvim plugins](/tools/text-editor/vim-plugins.md).

## Links

* [Your problem with Vim is that you don't grok vi](https://stackoverflow.com/questions/1218390/what-is-your-most-productive-shortcut-with-vim/1220118#1220118).
* [Interactive vim tutorial](https://www.openvim.com/)
* [Vim Novice Videos](http://derekwyatt.org/vim/tutorials/novice/) by Derek Wyatt.
* [Vimcasts](http://vimcasts.org/episodes/archive/) learn essential vim skills by Drew Neil.
* [TJ DeVries](https://www.youtube.com/c/TJDeVries/videos) YouTube channel by a core contributor to Neovim and the author of the excellent [telescope.nvim](https://github.com/nvim-telescope/telescope.nvim) plugin.
* [ThePrimeagen](https://www.youtube.com/c/ThePrimeagen/videos) - VIMtertainer extraordinaire.
* [Vim anti-patterns](https://sanctum.geek.nz/arabesque/vim-anti-patterns/) - what not to do in vim.
* [vim\_talk\_notes](https://github.com/r00k/vim_talk_notes) write code faster: expert-level vim by Ben Orenstein
* [Let Vim do the typing](https://georgebrock.github.io/talks/vim-completion/) and [talk](https://www.youtube.com/watch?v=3TX3kV3TICU) by \_\*\*\_George Brocklehurst
* [VimGolf](http://www.vimgolf.com/) pick a challenge, fire up Vim and share the result.
* Examples of `.vimrc` files: [Chris Hunt](https://github.com/chrishunt/dot-files/blob/master/.vimrc) and [Gary Bernhardt](https://github.com/garybernhardt/dotfiles/blob/master/.vimrc).
* `init.vim` and `init.lua` configs I take inspiration from: [ThePrimeagen](https://github.com/ThePrimeagen/.dotfiles/tree/master/nvim/.config/nvim), [TJ DeVries](https://github.com/tjdevries/config_manager/tree/master/xdg_config/nvim)

## Other editors I use

* [VSCodium](https://vscodium.com/) - a community-driven, freely-licensed binary distribution of Microsoft's editor VSCode. Second best choice for me after Neovim.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.stojanow.com/tools/text-editor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.