Edit: Unfortunately, the images originally included in this post are gone, because of hosting problems in late 2009. My apologies.
I touched on an idea in the last post, of running a tabbed terminal emulator on a graphical desktop, and partitioning each emulator with dvtm. The idea was that it would allow an immense number of console-based programs to simultaneously co-exist, in a way that really has no impediment aside from your own needs and your ability to keep track of all those things.
The fact is though, that part of that idea stemmed from using both dvtm and screen in tandem on my Thinkpad, which is running completely without X and throwing everything against the framebuffer. And the amount of flexibility there is likewise staggering.
Maybe this screenshot (framebuffershot?) will give you an idea.
See, screen itself can do split screens, and you can bounce between applications individually, pane by pane. And as you can see there, dvtm is quite happy to further segment the available screen space into smaller and smaller areas.
It’s like those Russian dolls.
Perhaps its just me, because of the proximity of it all, and the immediacy of how flexible the two are together. But to know that screen itself is keeping everything neatly bundled together, and can show two or three at a time, and all that on an 800×600 screen … it’s staggering, and cool at the same time.
This is a clean installation of Crux, by the way. Start times at 550Mhz are just over 12 seconds, and I have .screenrc set up to spawn dvtm with elinks, calcurse and alpine all at once. moc is on one window, mc on another, and htop (in a much-customized state) is on the last.
And best of all, I have my customized version of MPlayer for watching my DVD rips on the framebuffer. What in the world was I bothering with X for?! 😯
Could you post your .screenrc?
Yup, but I’m almost embarrassed because it’s so primitive.
screen -t mocp 0 mocp
screen -t mc 1 mc
screen -t htop 2 htop
screen -t dvtm 9 dvtm vim alpine elinks
I changed calcurse to vim recently, so I can jump to my vimwiki first.
I could switch if wasn’t for the fact that framebuffers can’t use widescreen or bigger resolutions.
@thealphanerd – they can use widescreen, if your hardware supports it. Install hwinfo and run “hwinfo –framebuffer” to get a list of modes your hardware supports, which you can then use in vga= at boot. I have two widescreen laptops and the framebuffer on each runs at the full, native, widescreen res.
Thanks for this post, I am interested in.
you really got me laughing with russian matryoshkas…
love you blog
Pingback: More lightweight diversions « Motho ke motho ka botho
Can’t you just use screen with the vertical split patch?
Pingback: Howto: Desktop “widgets” for the console « Motho ke motho ka botho
Pingback: Cool and fun: screen-vs inside Yakuake « Motho ke motho ka botho
Pingback: Rounding out a terminal-based Debian system « Motho ke motho ka botho
Pingback: One mine, one not « Motho ke motho ka botho
Could one use screen to open multiple of dvtm and treat it as virtual desktops? Or combine it with twin so one has tiling and stacking terminal window managers within reach.
I don’t see why not. I believe you can run more than one instance of screen; whether or not multiple dvtm sessions is possible … well, I don’t know. but I am willing to try. 🙂
Pingback: A comfortable arrangement: Musca and screen « Motho ke motho ka botho
I’m a bit curious of your combination Mr. Mandla, why don’t use just TMUX?
I’ve tried tmux, and I liked it but I couldn’t figure out how to do some of the things I was accustomed to in screen — most notably the blanker or “screensaver” effect. I don’t know if that’s possible in tmux, but it was something I enjoyed from screen that I couldn’t get working in tmux. So here I am. … 🙂