ed(1) scripts can be used to transform text. Starting with a default Vagrantfile and "playing" each transform 001.ed, 002.ed, etc on it.
What I haven't seen yet are (1) state-modifying workflows and (2) domain-specific macro "loadouts."
For example, editing something and re-opening the same file after incrementing a variable.
And for the second, sourcing a "writing a novel" .ed script so that certain keymaps help with that, versus a coding loadout where keymaps help with refactoring.
Maybe it gets too confusing or complex, maintaining the tooling instead of getting to the actual work. But it aligns with the desire to customize one's computing environment.
ed(1) scripts can be used to transform text. Starting with a default Vagrantfile and "playing" each transform 001.ed, 002.ed, etc on it.
What I haven't seen yet are (1) state-modifying workflows and (2) domain-specific macro "loadouts."
For example, editing something and re-opening the same file after incrementing a variable.
And for the second, sourcing a "writing a novel" .ed script so that certain keymaps help with that, versus a coding loadout where keymaps help with refactoring.
Maybe it gets too confusing or complex, maintaining the tooling instead of getting to the actual work. But it aligns with the desire to customize one's computing environment.