3 ms·
Hmm, maybe. That's why I added the "text editor" suffix to the title, to be specific about what I was referring to. "Interactive command-line app" could also be
by jmmv 6y ago
Hmm, maybe. That's why I added the "text editor" suffix to the title, to be specific about what I was referring to. "Interactive command-line app" could also be misinterpreted because any CLI that asks for user input on a line-oriented manner (e.g. a REPL) would qualify, right?
- MaxBarraclough 6y ago> I added the "text editor" suffix As it's pretty vital information I don't think it belongs in a subheading, which may be chopped when the post is submitted to a site like HN. > any CLI that asks for user input on a line-oriented manner (e.g. a REPL) would qualify, right? That's true, but it's more specific than console app. It would be a bit cumbersome to restate what TUI means in less obscure terms, although it wouldn't be the longest title known to man: Unit-testing a full-screen interactive command-line application.
- rualca 6y ago> That's why I added the "text editor" suffix to the title, to be specific about what I was referring to. That was not good not clear, as there are command line text editors like ed. https://en.wikipedia.org/wiki/Ed_(text_editor) https://en.wikipedia.org/wiki/Ed_(text_editor) Another way to disambiguate TUIs vs CLIs is to refer to the frameworks used to develop the app. For instance, mentioning ncurses or ncurses-based app is also frequently used to refer to TUIs.