Tabbed has a port. I just tried it, and I think it looks a lot better than the native urxvt support for tabs. Tryxterm is intended to remain quite spartan on interface features so doesn't have tabs.
Two options that I can think of:
- Run tmux or screen inside the terminal for multiple shells.
- Take advantage of the flexibility of X11 and the xembed protocol with tools like tabbed.
urxvt -pe tabbed if you want to try the latter.I had a look at tabbed and it wasn't immediately obvious what it provided.xterm is intended to remain quite spartan on interface features so doesn't have tabs.
Two options that I can think of:
- Run tmux or screen inside the terminal for multiple shells.
- Take advantage of the flexibility of X11 and the xembed protocol with tools like tabbed.
I used LXTerminal, part of LXDE, for quite a while because of tabs. I could never get the hang of Xterm.I am using urxvt which has shortcuts for tabs, new windows. Doe xterm has the same, please?
Thank you.
The suckless community tend to be quite good with their manpages but I suspect this kind of minimalistic tooling hasn't attracted enough interest for a wide selection of guides.I had a look at tabbed and it wasn't immediately obvious what it provided.
Is there a guide to what it gives you?
$ tabbed -c xterm -intotabbed urxvt -embed like the man page recommends and it worked out quite nicely.But is not better tmux that only runs a shells and not terminal emulators?I just tried it, and I think it looks a lot better than the native urxvt support for tabs
But is not better tmux that only runs a shells and not terminal emulators?
For other programs has tabbed more sense.
Then perhaps with a lightweight terminal emulator, something like:Unless you use nested tmux, which I avoided so far.
Yep. I moved off tilix and settled on one uxterm/foot per host. Works well and you get distinct windows, so you have to be more deliberate about closing them.The problem I have with tmux is all the remote logins. I don't want to open tmux on the local host, I have them on the remote one. But then you have sessions in an xterm group that you cannot switch between with tmux. Unless you use nested tmux, which I avoided so far.
bindkey ^[[18~ prev
bindkey ^[[19~ next
I usually just have one xterm per screen session. If it's a remote session, start an xterm for it, ssh to the remote host and attach the screen session. Nested multi-screen screen or tmux sessions gets too confusing. Well, I guess you could use something like horizontal or vertical splits to separate remote sessions, but I usually just use separate xterms. Where this gets a bit more important is when you're working on a console only with no X.The problem I have with tmux is all the remote logins. I don't want to open tmux on the local host, I have them on the remote one. But then you have sessions in an xterm group that you cannot switch between with tmux. Unless you use nested tmux, which I avoided so far.