Using vim as a Flutter IDE - what works, what doesn't
summary
Claim: Vim is a viable Flutter IDE after two years of daily use, with practical tooling rather than magic. Uses Neovim plus coc-flutter for language features, Git blame for history, AG (the Silver Surfer) for fast code search, Copilot plugin, and Kitty terminal with a PID-file hot‑reload workflow wired into makefiles. Refactorings from IntelliJ are not missed, debugging stays mostly print-based, and the setup works reliably for development, builds, and CI‑mirroring of local runs.
AI-written summary · about
chapters (12)
- 0:00Introduction and Vim basics
- 1:07Why use Vim for Flutter
- 5:34Switching to Vim as daily driver
- 12:12Essential Vim shortcuts and workflow
- 14:38Plugins and IDE-like features
- 18:34File navigation and search tools
- 21:46Git and debugging in Vim
- 24:16Makefiles for Flutter workflow
- 26:44Terminal emulators and Kitty
- 29:55Debugging strategies
- 31:42Reading manuals and hidden features
- 32:46Why Vim works for me
related talks
40mRevving up your Flutter IDE
12mVim in the Modern Era: Leveraging a Small Editor for Big Results
38mFlutter: A Path of Vines and Flowers
14mVIM for Victory
27mFlutter After Hello World
38mThe IDE Flutter Deserves
47mFlutter, FFI and Fun: Windows Development with Dart and Win32
44mEverything You Need to Know about Vim and Text on Linux