Instead of fumbling around in a live demonstration, we can just play back the user inputs one by one. This is another weaponizing Emacs style feature. By recording user inputs, we can play out sequences of inputs reliably. The results will look identical to the development experience, encoding literally anything Emacs does within a scripted presentation.
Requirements:unread-command-events
is a likely implementation. We can pretend to input keys in a blocking animation loop. Blocking would eliminate issues where two animations could run at once or the user fat-fingers an event right after starting the playback.#+attr_dslide_macro: :config1 value :config2 value :keys '(list of input events one by one encoding the macro)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4