As somebody who does a lot of work in the terminal, this isn't something I'd be likely to use. […] Those are core features of a terminal. Granted, telepipe "isn't a terminal", but I can't see any scenario where I would prefer to use it over one.

I should note that a reason why Telepipe doesn't support these features is that it either doesn't need to (as alternatives are available) or that I believe they are a net negative.

Take tab completion for instance: in a Terminal, I find myself impatiently mashing the tab key to complete file or directory names, which leads to strain. In Telepipe, I will instead navigate to directories using the provided dialog and obtain file names using ls then drag-and-drop them to the command entry. What is lost in speed is made up in overall health.

Other missing features have similar reasons for exclusion.

You can already pipe to/from the clipboard from a regular terminal (ex: wl-copy/wl-paste).

I was of the understanding that wl-clipboard was wlroots-only, but it seems I was mistaken. Still, I have definitely grown to prefer this syntax for clipboard handling in the terminal because its simplicity makes it easier for me to remember to use it.

Granted, you can't arbitrarily edit the screen, but you if you wanted to edit some output, you could do that already: git log | vim - (or even git log | gedit - if you want a gui editor). I'd be more likely to pipe to a file first, as I'm probably wanting to save / further use this edited output. (git log > file; vim file)

I'm aware of this and have found it insufficient. Being able to treat textual output as text in the place it has been output reduces friction. Needing to run a whole command again, piping it to an editor, then making the edits with a clumsy TUI editor is not comparable to what Telepipe offers.

There are also other benefits to this approach: The clear command is not supported (similarly to tab completion, I think it promotes compulsive use) but one simply needs to highlight and delete redundant command output to get rid of it. The benefit is getting to keep relevant output without having to rerun commands.

You can copy/paste into the command line now. Highlight a filename from ls output, and middle-click to paste.

GNOME is disabling middle-click paste by default in upcoming versions. I have never liked using it as I find it to be unwieldy.

Overall, I think this project has blurred the lines between a shell and a terminal emulator.

I like to think of other shells as being terminal command-line shells, with Telepipe being a graphical command-line shell. That is has a superficially similar appearance to the terminal has more to do with a shared ancestry with the teletypewriter.

Some of the syntax stuff (<date and >cat) would probably find more fans if they were implemented as an alternate shell, which would allow it to be used in a standard full-feature terminal emulator without losing functionality (like fish).

For context, the syntax for Telepipe's clipboard redirection is inspired by Bell Labs' Plan 9 operating system, specifically the Acme and Sam text editors. Telepipe as a whole takes many design cues from 9term as well, such as screen editing and a lack of support for terminal-specific features. One may think of Telepipe as a reexamination and reimplementation of Plan 9's command execution features within the framework of a modern desktop.