[Dr_Birdbrain]

You might be underestimating vim ;)

Key point is that vim macros are interactive. You don’t just write a script that runs autonomously, you say “ok, for the next transformation do this macro. Oh wait, except for that, in the next 500 lines do this other thing.” You write the macro, then the next macro, adjust on the fly.

[rlupi]

From the article:

> Our initiative began with a monumental task of converting more than 15,000 Enzyme test cases, which translated to more than 10,000 potential engineering hours

That's a lot of editing.

[gray_-_wolf]

Out of curiosity, can you drop into edit session during the macro? It is some time since I last used vim, so I do not recall, but in emacs you can record a macro along the lines of "do A, do B, drop to edit session letting user do whatever, do C, do D". Is that possible with vim macros?

[slaymaker1907]

I don't think so since you need to leave edit mode to terminate the macro.

[suplix]

Just use —- calculating… —- 2 macros.

[pqb]

That sounds interesting! Would you mind sharing some links to the articles or videos that focus on this possibility?

[duffmancd]

This Vimcast (http://vimcasts.org/episodes/converting-markdown-to-structur...) recording is an example of a quite complex macro for converting (a specific file's) markdown to HTML. At the beginning of the video you see that they save the macro to the "a" register. You can record macros of similar complexity to each of the other letters of the alphabet, to get some idea of the maximum complexity (though I tend to stick to about 3 or less in a single session).