My third session trying out #meow....

My strategy with trying meow is the same as #emacs when I switched from #vim in 2015. I'm noodling around with it on a branch of my dotfiles repo. Basically I give myself low pressure editting tasks to see if I'm really ready to roll with the new setup. When I'm comfortable with that, I'll try it for work tasks. My current task is editing my init.el file (using meow bindings) to convert it to #meow. I was able to remove all the evil config successfully but it is incredibly awkward atm. Other than not really getting meow bindings, the other stumbling points are kind of surprising since so much of this is very automatic after many decades:

1. Window (in the emacs sense) management. I relied on C-w commands provided by evil. I've been able to replace these with various other commands under the C-w binding, mostly leveraging the built-in winmove.

2. Undo and redo. Although meow has an undo, there's no redo binding. I don't like the emacs bindings, so I decided to go more mainstream on this one and use C-z and S-C-z for undo and redo respectively. I've never used C-z to suspend emacs, so it doesn't seem like a huge loss.

3. Saving files. I used evil commands for these. The emacs bindings are ok, so I'm training myself to use C-x C-s. I'm already used to C-x C-c so this seems consistent.

4. Searching and replacing in current buffer. I really liked / and the :s///gc vim commands. C-s is a poor substitute so far. Still working on this.

Surprisingly, other than text editing, things are going well. I'm able to use 90% of emacs without issue. I still don't grok meow bindings yet, so next is getting up to speed on actually editing.