⌨️ Subsystem Deep Dive

vim/

📁 vim/ 📄 7 files

Tutorial: vim

This project implements a robust Vim emulation engine that processes user keystrokes through a strict state machine rather than simple event handlers. It decouples the intent (transitions) from the action (operators) and the geometry (motions), allowing complex commands like "delete inner word" to be executed safely via a unified context interface.

flowchart TD A0["Vim State Machine"] A1["Input Transition Logic"] A2["Motion Resolution"] A3["Operator Execution"] A4["Text Objects"] A5["Operator Context"] A1 -->|"Transitions between states of"| A0 A1 -->|"Triggers commands from"| A3 A1 -->|"Calculates navigation using"| A2 A3 -->|"Determines action range via"| A2 A3 -->|"Selects semantic units via"| A4 A3 -->|"Applies edits to"| A5

Chapters

  1. Vim State Machine
  2. Input Transition Logic
  3. Motion Resolution
  4. Operator Execution
  5. Text Objects
  6. Operator Context

Generated by Code IQ

Files in this section

01_vim_state_machine.md
Chapter 1: Vim State Machine
Welcome to the heart of the editor! If you have ever wondered why Vim feels so different from editors like Notepad or V…
02_input_transition_logic.md
Chapter 2: Input Transition Logic
In the previous chapter, Vim State Machine, we learned that Vim acts like a car with a manual transmission. It has diff…
03_motion_resolution.md
Chapter 3: Motion Resolution
In the previous chapter, Input Transition Logic, we looked at how Vim acts like a switchboard operator. It receives a k…
04_operator_execution.md
Chapter 4: Operator Execution
In the previous chapter, Motion Resolution, we built the "GPS" for our editor. We learned how to calculate where the cu…
05_text_objects.md
Chapter 5: Text Objects
In the previous chapter, Operator Execution, we learned how to combine an Operator (like Delete) with a Motion (like "m…
06_operator_context.md
Chapter 6: Operator Context
In the previous chapter, Text Objects, we learned how to select complex chunks of text, like "inside quotes."