3 ms·
Tried it several months and left unimpressed. While by what the product aspires to be, it could be the IDE for command line, it's far from that. The only differ
by noway421 9y ago
Tried it several months and left unimpressed. While by what the product aspires to be, it could be the IDE for command line, it's far from that. The only difference is essentially autocomplete, which is not intelligent (and probably can't be, nothing along the lines of parsing --help or man pages) and felt clunky when trying to edit part of a command and then try to get another "suggestion".
With zsh's built-in Ctrl+R it's at least possible to reduce list of suggestion and then travel up the history in those suggestions. While the more powerful fzf will give you the list of commands you've run in a selectable dropdown.
Upterm I think could be eliminating entire classes of tools which sometimes are unnecesary complex. Server automation could be part of pre-saved playbooks which are saved to your terminal history and can be easily brought up and run according to rules. Curl arguments could be arranged in a way where they are actually managable. Parsing --help and man pages (which is possible, there is a workable implementation in fish AFAIK). Upterm is in position to take on that functionality, but right now it's not much more than already mentioned hyper, but with custom handled prompt line.
- shockone 9y agoThanks for the feedback! It's true that we're far from where we want to be, but we're steadily - event if slowly - moving into that direction. Also, we recently integrated monaco-editor by Microsoft, so editing is much less clunky than it was before.