> For the complete documentation index, see [llms.txt](https://book.vim-bootstrap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.vim-bootstrap.com/getting-started/readme.md). # Welcome ![Vim & Neovim Daily Solutions](https://3731655058-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcSSp5EAqOTLeOpyk422X%2Fuploads%2Fgit-blob-76c13c2673e77e9f62ee2ef8b45a451e6e558c46%2F00-cover.png?alt=media) Thank you SO MUCH for getting this book! **Vim & Neovim Daily Solutions** is a hands-on guide to becoming productive with Vim and Neovim. We wrote this book because we believe Vim is more than an editor — it's a way of thinking about text manipulation that, once internalized, makes every other tool feel clumsy by comparison. Whether you're a developer who just discovered Vim, or someone who has been using it for years and wants to modernize their workflow with Neovim's Lua ecosystem, this book has something for you. Every chapter is packed with practical examples you can try immediately, not just theory. ## How to Read This Book The chapters are organized as a progressive learning path — start from the beginning if you're new to Vim, or jump directly to any section that interests you. Each chapter is self-contained, though they build on concepts introduced in earlier ones: 1. **Getting Started** (Chapters 0-4): Modes, navigation, text objects, registers — the foundation 2. **Core Editing Skills** (Chapters 5-9): Buffers, search/replace, regex, macros, mappings 3. **Configuration** (Chapters 10-11): Vimscript and Lua configuration 4. **Modern Neovim** (Chapters 12-19): Plugins, LSP, Treesitter, Telescope, completion, Git, debugging 5. **Advanced** (Chapters 20-21): Power-user workflows, scripting 6. **Appendix** (Chapters 22-23): Vim vs Neovim, resources ## What's New in v3.0 * Reorganized chapters with a progressive learning flow (beginner → advanced) * Related topics grouped together (search + regex + substitution in one chapter) * Full Neovim coverage: Lua configuration, LSP, Treesitter, Telescope, nvim-cmp * New chapters: Plugin Management, Git Integration, Debugging with DAP, Scripting * Vim vs Neovim comparison and migration guide * Updated resources for the modern ecosystem ## Authors * [**Thiago Avelino**](https://github.com/avelino) * [**Sérgio Araújo**](https://github.com/voyeg3r) ## Contact * Email: * Website: [editor-bootstrap.com](https://editor-bootstrap.com) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://book.vim-bootstrap.com/getting-started/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.