3 ms·

Although I don't like terminals, I think the article overstates the problems to significant degree. The fact that text editors running in terminal still manage

by zokier 4y ago

Although I don't like terminals, I think the article overstates the problems to significant degree. The fact that text editors running in terminal still manage to have "ide-like" experience (including mouse input!) proves that you can do a lot with terminals. I still think that trying to move beyond terminals is good idea, but it's important to distinguish what is impossible, and what is just ugly/hacky to do.

alokedesai 4y ago
Aloke from the Warp team here--you're totally right that some of these features (syntax highlighting) can be accomplished within the terminal using an editor. In a traditional terminal--you'd have to spend time configuring your shell to get this to work instead of getting these features by default. Some of these features are near-impossible given the current terminal-shell abstraction, however. For example, a traditional terminal has no concept of command input/output, which means that it can't suggest a next command to run based on the output of the previous command.
- vimda 4y ago
  > it can't suggest a next command to run based on the output of the previous command thefuck (https://github.com/nvbn/thefuck#how-it-works https://github.com/nvbn/thefuck#how-it-works) does exactly that...
  - alokedesai 4y ago
    We collaborated with thefuck to build our version of this :) TF is slightly different in that they actually _rerun_ your last command to get the output since they don't have access to command output
- zokier 4y ago
  > For example, a traditional terminal has no concept of command input/output, which means that it can't suggest a next command to run based on the output of the previous command. Neither does wayland or whatever. Point being that you can treat terminals as dumb character cell grid display with slightly wonky input mechanism and get quite far ignoring/working around all the traditional line-oriented stuff.

by zokier 4y ago

alokedesai 4y ago

Aloke from the Warp team here--you're totally right that some of these features (syntax highlighting) can be accomplished within the terminal using an editor. In a traditional terminal--you'd have to spend time configuring your shell to get this to work instead of getting these features by default. Some of these features are near-impossible given the current terminal-shell abstraction, however. For example, a traditional terminal has no concept of command input/output, which means that it can't suggest a next command to run based on the output of the previous command.

vimda 4y ago
> it can't suggest a next command to run based on the output of the previous command thefuck (https://github.com/nvbn/thefuck#how-it-works https://github.com/nvbn/thefuck#how-it-works) does exactly that...
- alokedesai 4y ago
  We collaborated with thefuck to build our version of this :) TF is slightly different in that they actually _rerun_ your last command to get the output since they don't have access to command output
zokier 4y ago
> For example, a traditional terminal has no concept of command input/output, which means that it can't suggest a next command to run based on the output of the previous command. Neither does wayland or whatever. Point being that you can treat terminals as dumb character cell grid display with slightly wonky input mechanism and get quite far ignoring/working around all the traditional line-oriented stuff.