Hi Nikolas!
Somehow, Codi.vim escaped from my attention, thanks for letting me know. At first glance, I would name the following differences:
- Codi.vim seems to work on a line-by-line basis. As far as I see, it doesn't attempt to guess the structure of the document. LitREPL (in theory) works with valid Markdown/Latex documents. It uses its own express-parsers to find out the location of multi-line code/result sections, and transforms the document accordingly, making it possible to emulate a WYSIWY(with a little delay)G.
- Codi.vim doesn't seem to preserve the state of the interpreter between editing sessions. LitREPL, in contrast, keeps the interpreter running with its stdin/stdout connected to pipes which are pinned as files in the filesystem. It is also possible to get direct access to the interpreter's shell. As a possible downside, LitREPL depends on certain Posix tools to make things work.
- Codi.vim is implemented mostly in Vimscript, while LitREPL depends only on a
small Vim-script wrapper while most of the work is done by a command line
application written in Python. Probably, porting LitREPL to other editors should be an easier task.
- There are probably other minor differences like the support of ASCII '\r' symbol required for libraries like tqdm of Python (I see the support of Preprocessors in Codi.vim, so may be it does have the required support), the status of Ctrl+C support (LitREPL should support breaking the infinite loop), other behaviour on long-running commands (I plan to support the incremental output in LitREPL via files), etc.
BR,
Sergei