41–50 of 299 posts
It has a huge number of data formats it can visualize, but I haven't taken the time to go through them all. What I do know is that it is great for viewing CSVs in a terminal. Even if I don't use it for anything else, that alone merits an install from me.
In stark contrast to most GNU/*nix tools, I really liked MS-DOS's edit.com text editor. Unlike emacs or vim or even nano, it didn't have a bunch of invisible shortcut keys, just a Windows-like drop-down menu system (but rendered in DOS). You could easily browse through the menu hierarchy, but still memorize certain shortcuts that you often use (just like Windows). In later versions you could even use the mouse to sel…
I use vim, mutt, tig, newsboat, jless (if that counts) pretty much daily. Also a TUI Confluence client which I wrote and which I am the only user of as far as I know. Navigating Confluence becomes a breeze.
I use vim, mutt, tig, newsboat, jless (if that counts) pretty much daily. Also a TUI Confluence client which I wrote and which I am the only user of as far as I know. Navigating Confluence becomes a breeze.
Considering how many HTTP requests the web interface takes, I can see a dedicated Confluence client being a big win.
One of the neatest things of my client is that I can cycle through unified diffs of the history of one page with a single key stroke. It's not perfect (macros are a problem) but good enough for me.
In stark contrast to most GNU/*nix tools, I really liked MS-DOS's edit.com text editor. Unlike emacs or vim or even nano, it didn't have a bunch of invisible shortcut keys, just a Windows-like drop-down menu system (but rendered in DOS). You could easily browse through the menu hierarchy, but still memorize certain shortcuts that you often use (just like Windows). In later versions you could even use the mouse to sel…
> Unlike emacs or vim or even nano, it didn't have a bunch of invisible shortcut keys, just a Windows-like drop-down menu system (but rendered in DOS). You might like "joe", which was inspired by WordStar: https://joe-editor.sourceforge.io/ >
Not particularly high-level, but representing common TUI designs and usage patterns on Unix: Slrn, Mutt, Ncdu. https://en.wikipedia.org/wiki/Slrn https://en.wikipedia.org/wiki/Mutt_(email_client) https://en.wikipedia.org/wiki/Ncdu
Thanks for listing it.
Midnight Commander immediately comes to mind, but also Borland's C++ compiler.
I believe Norton Commander was the original product (for MS DOS), Midnight Commander is its open-source cross-platform clone. FAR Manager is another notable TUI clone of NC. Windows Commander/Total Commander are also NC clones, but implemented as GUI instead of TUI. NC was one of the most convenient UIs for managing files, it’s a pity none of the major operating systems adopted this style for their default file manag…
As someone who writes software for moderately boring business operations, I've been wondering making terminal-based apps with lots of keyboard shortcuts would lead to a more productive end user than writing a web app. I've been looking at https://github.com/gui-cs/Terminal.Gui but haven't tried it yet.
I'm old enough to have used green screen CICS apps in a bank. The things that really helped productivity were: * Information dense screens (despite having only 80x25 characters) * Responsiveness * Reliable type-ahead when the responsiveness wasn't quite good enough
IBM ISPF suite is gorgeous.