As I've found with nvim using the lazy-vim config, no. That program, for example, requires a separate clipboard manager if you want to copy between it and your system.

Which terminal emulator copies with ctrl+c?

I agree that CLI and keyboard driven systems are powerful and should be further developed. New terminal emulators like Kitty, Nerd fonts, and Lazyvim show what’s possible.

I would too!! I'm mulling over using it on my personal projects - I still create tickets, open PRs, even though they are one-man-projects, so working the git email in there will probably happen next weekend. So excited already :D

An hour gave me the gist indeed, I'm sure there's many more to learn, but the concept already blew my mind. And it fits the terminal-based workflow I'm slowly creeping towards.

No hope for my workplace through, the people there are still clinging to office365 mail without access for 3rd party clients. But they're chill so I am too, that's our (unspoken) deal :)

I would actually like to make a Diff activity for ActivityPub and unleash total chaos, whos with me?

In general, I agree that you can always use the CLI raw, but a frontend is a lot more friendly for many. It's the reason some people prefer TUI over CLI as well (some people really like lazygit and lazydocker which are just frontends wrapping git and docker CLI calls and presenting it in a TUI). A TUI/GUI can structure information in panels, it can be more context-sensitive and it can help provide visual representations of the operation.

Also, wrapping CLI commands (whether through a GUI or a TUI) means the wrapper can automatically combine the commands in whichever way it's best for a particular goal, or more conveniently set up batch processing... it's helpful for people who don't like having to make their own scripts, or craft long oneliners.

Plus: lets say you have your computer hooked to your TV and don't have space for a keyboard (but can use a small wireless mouse on the arm of your couch), a GUI wrapper that allows you to perform operations with just a mouse can be very convenient.

I don't know what kind of GUIs are you imagining, but I've hardly ever seen 1-to-1 recreations to a single individual command (unless that command is extremely complex or a graphical representation would be actually useful).

Some examples:

Gparted creates a job list of terminal commands for the disk manipulation, but it presents a graphical representation of the disks before you actually commit to executing the commands internally, so you can see what would be the result of the changes in the GUI side before actually pressing the button that actually executes parted, fdisk, mkfs, resize2fs, etc. (they do wrap the commands when it comes to executing the changes), without you needing to go through the steps and specific syntax of each of them on your own.

There are wrappers to ffmpeg for video editing or transcoding that some people find convenient for discoverability of the options available and/or to have a limited list of presets / sanitized options for those who don't want to bother creating their own scripts. Sometimes also showing video previews for the graphical representation (useful when the operation is about cropping the image, or picking the exact millisecond where to cut). An example is LosslessCut, they keep a log of the ffmpeg calls.. or maybe Shutter Encoder (press Alt+C to see the console commands).

In Synaptic, the GUI package manager, pressing "Apply" calls the appropriate APT commands as a CLI app inside a VTE with the selection of the packages you have decided to add/remove/update, which you have previously selected in the listing that is generated from the GUI view of the app. Some people like having a graphical detailed listing which might be useful for conveniently browsing packages and seeing their detailed description, while still you get the raw information and accurate log from the installation that you would get when you are just using the CLI.

Have you seen debugging in an ide, they usually just run gdb / lldb commands

yeah good GUIs are really important for people who use a lot of programs lol.

I can't remember everything at once, I've got better things to do

CLI: Welcome back my friend, forgot a command or argument? Just type --help and read the super terse and bullshit free txt file in less time it takes for the GUI startup animations to finish. Too long? Type | grep to directly search for it in less time than it takes for the search button to expand and let you start typing! Realize you keep doing the same few steps? Just write a script instead of memorizing what specific sequence of buttons to click or hope that the GUI remembers where you left off! Need to tell a team member how to do something? Just send them the commands or a full script in chat instead of jumping on a video call and walking them through which of these abstract, indescribable icons they need to click which they'll definitely get wrong and open some weird submenu you then have to tell them how to leave!

GUI: Ooh a GPU and gigabytes of VRAM just for my animations? You shouldn't have! Ooh you mouseovered something for one millisecond while moving it to the actual thing you want? Let me lag the entire window and cover up the thing you wanted with this popup that takes longer to disappear the more irrelevant it is! Also none of the text in mouseover popups is selectable so you can't copy from it even if you did need it (Visual Studio static analysis messages I'm looking at you). Still need help? Well you first have to find where the help button is if there even is one! We're increasingly not including help files because it "should" "just" be intuitive. Or just watch a 10 minute video walking through how to do something that could have been two lines in the terminal, stupid! Want to automate something that takes like ten clicks because we hid everything in nested submenus to "avoid clutter"? Go ahead and install a third party macro suite and record your mouse clicks and movements that will break as soon as the next update drops and slightly shift the margins around!

I see that you don't use a shell with completions.

Isn't the T for "text"? (ie. "Text User Interface")

I mean, in the context of Unix systems it's most likely gonna be within a terminal emulator, but in theory you can have a TUI inside an SDL window rendering the text there (specially when they are ports from other systems where they might be using different character sets than whats available in terminals.. or if they want to force a specific font).

The only example that comes to my head right now is ZZT, but I believe there are many games on Steam that use a TUI rendered within their own program, not a terminal.

Thanks! I guess something like vim would count as a TUI then.

Slackware was my first linux back in the day. :)

Glad you found something interesting :)

Waiting for others to do something for you is the wrong approach. Get off your ass and be the developer. Creating an interface for a tool is no rocket science.

Oh what’s tldr?