Emacs's term-mode already solves all of these supposed problems. I say supposed because they're really not all that big of a deal. OK, bash making it difficult to go backwards to previous lines is... annoying, at least until you press C-x C-e and do what you want anyway. The use of a mouse for something text-centered is pretty much foreign to me, too.
And of course for anyone who doesn't like term there's always shell and eshell. And if neither of those will suffice vterm is readily available from MELPA.
As much as I'd like to encourage the rethinking of input methods, any terminal with a "Pricing" page is an instant nope from me. My current terminal is Open Source and while it's not perfect, it's also Free. That matters more to me than mouse input or IDE autosuggestions. If you're going to treat Linux users as a second-class citizen and charge for corporate usage, who are you hoping your target audience will be? Fra…
The app is 100% free for any and all individuals. The business plan is to create collaborative and cloud-based features that businesses will be willing to pay for. Please check out our pricing page to learn more. Please note that our business model is not about collecting and monetizing any of your personal data. https://www.warp.dev/privacy
>>My current terminal is Open Source and while it's not perfect, it's also Free.
>The app is 100% free for any and all individuals.
I assume the usage of the upper-case F in "Free" indicated libre, not gratis. Your comment is about the latter.
> This post is about why terminal-based input seems stuck in the 80s It's actually more 60s/70s, when the first terminals, command-line prompts, and shells were built. The reason why it's stuck there is technology has only improved iteratively rather than revolutionarily. The "lets add another layer of abstraction" form of innovation, rather than outside-the-box thinking and reinvention. The fact that we still write…
What would you prefer it to be? Audio recording of spoken words? Diagrams like Labview?
Guys, it doesn't matter if you can edit terminal input in vim. If there's a way to do it in an even more ergonomic / user-friendly way, that's not intrinsically a bad thing. This entire comment thread makes us sound like tech-grognards. Warp's pricing model is a whole other issue though.
What's the problem with the pricing? It seems pretty fair to me, free for users and paid for teams basically.
Guys, it doesn't matter if you can edit terminal input in vim. If there's a way to do it in an even more ergonomic / user-friendly way, that's not intrinsically a bad thing. This entire comment thread makes us sound like tech-grognards. Warp's pricing model is a whole other issue though.
And who decided that Warp's method is more ergonomic / user-friendly with such objective proof that it cannot be argued over?
Maybe some user research? It can be argued for sure though, everything can be argued over all the time forever.
TO better understand the architecture, how will this work if I want to use the shell in vi mode? IIUC that would not be possible with their setup, right? Warp would need to implement a vi mode, correct? Is it possible to work with vim in warp?
You can launch vim within Warp without any problems, but vi/vim mode for the line editor itself isn't supported in Warp just yet. You're correct that this is because we'd need to implement VI mode ourselves (tracking issue here [1] if you are interested).
This is the tradeoff of building our own editor instead of using the shell's--we can build features that wouldn't be possible in the shell directly but it requires us to build features that already exist in the shell from scratch. So far, this tradeoff has been well-worth it to build what we think is a better experience when using the terminal.
> This post is about why terminal-based input seems stuck in the 80s It's actually more 60s/70s, when the first terminals, command-line prompts, and shells were built. The reason why it's stuck there is technology has only improved iteratively rather than revolutionarily. The "lets add another layer of abstraction" form of innovation, rather than outside-the-box thinking and reinvention. The fact that we still write…
What would you prefer it to be? Audio recording of spoken words? Diagrams like Labview?
Ideally? That holographic interface Tony Stark uses. I would settle for a combination of SolidWorks and Visual Basic. SoldWorks to model and visualize the whole thing, pick it apart, run it. Visual Basic to assemble DCOM objects, add simple logic, design an interface. Export/import SolidWorks models and connect them to new models to re-use a whole "machine". Keep a corporate library of "machines", import one to do what you need, fork it and make a new one if it doesn't do what you want.
I can edit the terminal input line with full vim-mode in my shell (zsh). In fact, in normal mode I can even hit 'v' and edit the line in a full vim session to zip around however I want, do completions, etc. It's pretty close to the platonic ideal method of input I could imagine.
This is also available in bash. In emacs input mode (aka the default) one can press C-x C-e to edit the current command in an editor.