I was excited to learn about two new terminal emulator app which seemed to have a lot of cool new features, warp and wave. Then I looked closer and found that both are a no go for me.
Warp is closed source and you need to create an account to use your terminal. Jebus Christus, no, thanks, but no.
Wave is an Electron app. While that’s better than not having a Linux version, I’ve seen how Electron apps behave. They are the ones which hog all memory and get killed by the OS first. So that’s a no from me too.
I guess I keep my Tilix for now.
Warp is closed source and [needs a mandatory account, and] Wave is an Electron app.
I can’t see the benefit of fancy terminal emulators. I use plain old Konsole (mostly on Plasma) and as long as it has good history search and multiple tabs, I’m good.
Don’t even need tabs with
screenTook me weeks to figure out a way to run a script at startup in a konsole window that gets hidden but continues running in the background. Tmux could do it but I found it cumbersome.
screen did the trick with a single command.
plain old Konsole
Come on now, it’s pretty active! Cf https://invent.kde.org/utilities/konsole/-/commits/master/?ref_type=HEADS 13hrs ago, a new feature weeks ago and https://konsole.kde.org/changelog.html
I know it’s active, but most of the stuff being added is not something I use. “Plain old” is a figure of speech for something that is pretty “vanilla”.
That is the Luddites argument against progressing anything. There are many problems with current terminal emulators that these newer ones are trying to fix and make the terminal experience better overall. Terminals as they currently work were designed the way they are to talk to dumb typewriters with a screen (that’s right, not keyboards, digital typewriters). And they have barely changed at all since then.
Personally looking at these terminals they have a lot of niceties that I would love to use. But IMO these benefits are not worth the costs these particular terminals also have. One being closed source and requiring an account and the other being electron - no benefit is worth that. But to bury your head in the sand and claim they have no benefits at all is wrong.
Begin able to view images in the terminal would be amazing alone - just like you can cat a text file. I would hate to need to launch a GUI program every time I wanted to see what was inside a text file but that is exactly what I need to do for images or PDFs.
Being able to collapse the output of a command would be nice as well. The number of times I have had to scroll for days to get to the output of a previous command because I happen to run a noisy one but still want to check what something previously had done would save me quite a bit of annoyance. And being able to search just the last commands output would be great - like an after the fact, interactive grep with context. And being able to quickly copy the output of the last command would also be great.
Konsole can display images, as can kitty, alacritty, western, iterm2, etc. There’s quite a few formats to do so dating back decades. This isn’t new.
As for collapsing a command and it’s output that’s nice, but it’s not exactly game changing.
Lastly, searching explicitly your last command for a term with context would be much better suited to the shell to solve as it’d be terminal independent. Wouldn’t surprise me if under the hood it’s a bash script that takes whatever input you pass to bash, execs it, pipes stdout to tee, which passes it to a text file storing output and the console’s output too. Of course, you can always pipe it to fzf for a live grep with context if you have it set up right and remember to do so
I would agree just denying any advancements in favor of the “good ole way” is idiotic but nothing I’ve seen or that you’ve listed convinces me these are major advancements. Nor are these anything that couldn’t be solved at the shells level or with supplementary applications. Nice to have, if it weren’t electron or closed I would switch, but nothing groundbreaking
I doubt they’re outright rejecting any idea of progress. They’re likely just not convinced by what the fancy options offer
Konsole can display images, as can kitty alacritty, western, iterm2, etc.
They can now? I know it was possible in some niche terminals but never knew it was as wide spread as that.
but it’s not exactly game changing
None of these features on their own are game changing I agree. But lots of small nice to haves can end up being game changing overall. Again - I don’t think these terminals offer anywhere near enough to warrant their IMO massive downsides though. But I would love to see more innovation in the terminal emulator space.
Lastly, searching explicitly your last command for a term with context would be much better suited to the shell to solve as it’d be terminal independent.
I had a similar thought TBH. But the more I thought about it the more I came to see that in order to do this nicely - ie with inline scroll back or being able to collapse command output like these terminals do then you would basically need to implement a terminal emulator into the shell. Either way you are breaking down the wall between what a shell and a terminal emulator are doing. I would be interesting in exploring this from the shell side, though I cannot fault them from doing it from the emulator side either.
couldn’t be solved at the shells level or with supplementary applications
I think the key benefit here is integration rather than technical ability to do something. Making it easy and convenient to do goes a long way. There is a lot that can be made much nicer with things more tightly integrated together than trying to string up a bunch of disparate applications together - even if you can do it the integrated approach will give you a much more refined experience.
I doubt they’re outright rejecting any idea of progress
It sounds like an outright dismissal of new features to me.
TIL viu exists.
You do make some good points on it being terminalside, you’ve partially changed my mind there. I see the value now.
Also, you would be correct anything that allowed collapsing commands would be trivial to implement some sort of action per command and it’s output. Along with collapsing being easiest to do terminalside.
What I would love to see is a terminal that builds it’s own shell from scratch too rejecting the ancient ideas we have with bash. I still love bash but I’m curious what could come of it.
As for their luddite status their reply to my previous comment seems to show them to be a bit more open
Seriously though thanks for the good conversation and thought excersize
What I would love to see is a terminal that builds it’s own shell from scratch too rejecting the ancient ideas we have with bash. I still love bash but I’m curious what could come of it.
Thinking about it some more I am not sure that we would have to go that far. Well not in the longer term - short term we might for experimenting with ideas. I think one of the bigger problems ATM is the terminal does not understand what a shell is or its component parts. Terminals just display characters and move the cursor around the screen and send keyboard and now mouse input back to the command they run. They are also aware of alternative buffers and raw input mode and know about echoing characters back the the screen.
If we extended the terminals to also understand some shell concepts like the prompt, commands being typed and output from the commands and gave the shell some markers it could send along with these (like we do with color information ATM) the terminal would be able to use these to change how it displays each part and would open up a lot of new an interesting features. Could even add things like tooltip support or actions on clicking some bits of the text.
I am starting to see these terminals as experimenting on what we features could be enabled if we were not stuck on the current VT100 protocals. Though if we ever get wider adoption and generalisation of these ideas backed back into the protocals will be another question to consider.
I doubt they’re outright rejecting any idea of progress. They’re likely just not convinced by what the fancy options offer
Exactly. I don’t mind progress. But terminal emulators that does things you become dependant on, is not great in my opinion. Because what happens the day you only have a TTY to get things done? If you rely on all the fancy stuff, you would feel lost.
So yeah, I am not convinced that I need my terminal emulator to be fancy. But some people clearly are, looking at the rest of the comments on the post.
Nah man, the Luddites weren’t against technological progress, they were against the ruling class fucking us over. So I guess that goes for the terminal that needs a user account
Every tool has its job. Why should a TTY terminal emulator also be a image/pdf viewer?
Sweats in emacs
I think the issue fundamentally is that this isn’t what terminal emulators are. The terminal emulator initializes a TTY session and enters a shell environment (sh, zsh, fish, etc). The medium is text and cannot be anything else.
Begin able to view images in the terminal would be amazing alone - just like you can cat a text file. I would hate to need to launch a GUI program every time I wanted to see what was inside a text file but that is exactly what I need to do for images or PDFs.
Would be convenient. There are things like neofetch’s backend capabilities that magically embeds images, but I don’t know how it works and it might not be scalable.
Being able to collapse the output of a command would be nice as well.
Skill issue. Pipe your output to something (like a file or the “less” command)
I think the issue fundamentally is that this isn’t what terminal emulators are. The terminal emulator initializes a TTY session and enters a shell environment (sh, zsh, fish, etc). The medium is text and cannot be anything else.
This is 90s thinking. Why must terminal emulators only be text and only do things that a physical terminal could? What makes teminals so nice is not that they work on 90s technology. Some terminal emualtors can already display images. Which is great. And the ideas they are introducing are still fundamentally text based, but are geared towards structuring that texts a bit more than a constant stream of characters on the screen.
Skill issue. Pipe your output to something (like a file or the “less” command)
This is a convenience issue not a skill issue. Yes you can pipe output to things but you need to know before hand that you want to do that. And with less you lose that output once you close less. And with files you have to clean them up after the fact. Both of these are inconvenient and need to be thought of before you run a command. IMO it would be nice to just run a command and then be able to collapse or expand or search its output after the fact and not have to preempt everything beforehand.
The argument that you can already do that in a much less convenient way is not a very good argument.
This is 90s thinking. Why must terminal emulators only be text and only do things that a physical terminal could?
I keep trying to imagine what abandoning TTY interfaces in Linux would look like and I can’t comprehend the rework that would be required. It’s so fundamentally different.
For example, how would the SSH protocol work? How would that be compatible? Would we have to abandon SSH or always X forward?
There is definitely a pressure to extend beyond standard TTY. Tmux captures mouse action and has a window management system. fish shell has autocomplete. But both of these still use the same medium of text.
I may simply lack imagination.
Thinking about it some more I don’t think we would need to abandon the whole TTY to get a good set of the features. What is basically required for a lot of the features is more communication between the shell and the terminal. There is already some communication for basic things - like raw mode and alternative buffers, colors and even images. These are how TUI programs like vim or screen/tmux function and how you can exit them without losing what was previously in the buffer.
I wonder if markers for the prompt and start/end of command output would probably enable a lot smarter virtual terminals with only some minor additions to the VT100 protocols. Possibly some extra data could be sent as well - like optional tooltip data maybe or even supporting actions that when the user clicks something it can send a response back to the shell. Maybe like a retry button on previous commands for example.
There is quite a lot that could be done if the terminal and shells had better protocals to communicate between each other. I dont think these will change overnight though so seeing terminal emulators try out these features to find what people like/want to use IMO is a good thing to see where we can take things in the longer term.
Would we have to abandon SSH or always X forward
No we would not. At the end of the day a TTY is just a input and output pipe between the terminal and the program running on the shell with a specific protocal VT100 (or some bastardized version of that - looking at you xterm). This is what network protocals are as well - just with different protocals in play. So you can do a lot over that connection with changes to the protocals. No need for xforwarding at all.
There’s a lot of stuff other people have brought up in this post, but with correct ps and vesa configuration it’s been trivial to view images and pdfs under non-x sessions for decades.
Might I add the idea that your terminal emulator must support your shell is utterly ridiculous?
https://docs.waveterm.dev/reference/faq#what-shells-does-wave-terminal-support
https://docs.warp.dev/getting-started/using-warp-with-shells
Also Wave might be FOSS but if you look at the footer in their website it says it’s backed by venture capital… how would you estimate the chances it gets closed, paywalled or otherwise enshittified?
By default, sharing a sudo password between PTY sessions is not allowed by your operating system. This can be a frustration when using Waveterm because every command is treated as a separate PTY session. To get around this, Waveterm will cache your sudo password in local memory (not written to disk) and share it with a session when provided.
Holy crap, no thanks. That’s legit awful.
Might I add the idea that your terminal emulator must support your shell is utterly ridiculous?
TBH I am starting to come around to the idea of a tightly integrated shell and terminal emulator support. There are just things you cannot do with these being separate things. I am very tempted to explore the idea from the other end though - writing a shell that has a emulator built into it (like screen/tmux basically are). But I do think that this integration is needed for any per command features that is not just printing out a prompt.
It would be interesting to see what could be done with this type of integration but will likely break support for existing shells. Unless you maybe launch a shell for each command you run or something 🤔. Would like to seem more people experimenting with stuff like this and see what new things we could drive forward. We have been stuck with the current tty system since like the 80s to support devices that just dont exist anymore.
Philosophy aside, the practical issue with your terminal emulator having to support your shell is… that one does not use just one shell: what happens whenever you start a repl or an whatever program that has interactive sessions (say, for example, psql or parted)?
tightly integrated shell and terminal emulator support. There are just things you cannot do with these being separate things.
I can’t think of any, but I’m not the most creative person… what do you have in mind?
Having something that is like (say) tmux+fish could make sense, but only if it’s something that outweighs the lost flexibility of being able to combine <whatever shell you like> + <whatever terminal multiplexer you fancy>.
REPLs are basically shells. They behave the same way in every essential way. So the real question is support vs non-supported shells. But then that is easy - non supported shells fall back to just what a normal commands do ATM to process input/output. Other applications like TUIs are also easy to deal with as they already enter a different mode called raw mode - when a application requests that it can do what they currently do - switch to a new buffer and give full control to that one application.
I can’t think of any, but I’m not the most creative person… what do you have in mind?
Having smarter scroll back that knows the difference between a prompt/command and the output would let you do quite a few things that would be nice to have. Such as collapsing the output so you can only see the commands, keeping the command at the top of the screen even as other output scrolls off the top so you can always see what was running. Extra support for other UI elements could be nice to have as well - like tooltip support for blocks or similar.
All the shell - or really any application - needs to do is tell the terminal which bits of the output are witch. Like mark the start/end of the prompt, command and command output. Then the fallback is basically ignore the markers and print things out like it currently does.
And those are just random thoughts I have had over the last few days. These can be implemented in backwards compatible ways I believe and don’t need special support for specific shells - just needs to expand the VT100 protocols to be able to send more information between the terminal and shells/applications that are running. Much like how color, cursor positioning, entering/exiting raw mode etc are already done. Though I think some tight specialized integration might be a good start to explore these ideas before the protocols are formed.
Have you tried kitty? It’s seriously nice if you can live with the occasional “oh no I sshed to a server that doesn’t have the correct terminfo files and now none of the normal terminal navigation features work”
I like Kitty, but the terminfo stuff happens often enough for me that it’s a no-go.
Normally, I would fiddle with workarounds, but the author of Kitty has no plans to make Kitty play ball.
I just make
sshan alias that runsTERM=xterm /usr/bin/sshI ended up just making an alias for
s=kitten sshand then added my desktop to.ssh/configso now typings desktopdoes the trick!I use kitty as my term, I am a little jealous of some of the warp features though.
Wave has some cool features too though feels very clunky and busy ui
I tried warp but it was actually laggy and slow. Also I don’t like the account idea, but I was willing to let it slide if they built a much better terminal than what we have.
They didn’t.
i think id rather have the slightly worse option than to bother with accounts for every desktop app
Anyone using Wezterm?
Hell yeah, now that it finally works with Wayland on nvidia with explicit sync being added to the 555 drivers it’s been great for me
Yes. But sometimes pasting doesn’t work. Then I switch my focus to another window and back to WezTerm and it works again.
I’m thinking of switching back to Foot.
I use foot, it’s very bare bones, but I’m using zellig to get all the QoL features I could want!
i’ve never had this issue, my only gripe is that I set my system font to Jetbrains Mono using gnome tweaks which conflicts with Wezterm as it’s default font is also Jetbrains Mono
Is there any terminal that uses smooth scrolling, including for command output? Like, for example, you run
lsand the files scroll into view rather than the terminal abruptly jumping to the end of the output? I find the jarring transition disorienting and would like to get rid of it.I am waiting for Ghostty…
It’s made in Zig with a focus on performance while giving a good set of features.
Look it up!
I think Hyper was another Electron based terminal. And talking of terminal and Linux, there exists an electron based file manager for Linux as well. I wonder who exactly their target audience for that is though.
I’d really like one that let me see options for the command I’m typing. Like if I type “dd” it shows me some of the options for the dd command like “if=” or “conv=”. Is there a fancy term like that?
Using fish (shell, not emulator) gets you some of that.
That’s not something a terminal emulator should do - it’s a feature that belongs in your shell :)
The warp one seems to do that.
But that isn’t the job of the terminal, but the shell, isn’t it? I don’t know how they’d do that, but it feels like they’d have to assume a lot of stuff. On top of that, if you use multiplexers like tmux or embeded terminals like in emacs, for example, you’d most probably lose some of the features.
I don’t get how we need anything else than just a terminal that is fast, supports 256 colors (or true color, if you’re feeling fancy,) and changing the font.
deleted by creator
deleted by creator
