4 ms·

I started using stumpwm but I have a small problem that's been annoying me. I'm used to emacs, where if I kill a buffer while split, the killed buffer will be

I started using stumpwm but I have a small problem that's been annoying me. I'm used to emacs, where if I kill a buffer while split, the killed buffer will be replace by a hidden buffer, or the frame will unsplit. However, in stumpwm, sometimes I'll end a program while split, and I will be left with an ugly blank space where the program's window used to be. Then I have to manually unsplit and resplit to restore the layout I had before. Am I doing something wrong? I'm looking up how to get around this. I think it'll involve *destroy-window-hook* I just want stumpwm to take advantage of the whole screen at all times. Thanks.

d0m 12y ago
I think I know what you mean, but it's just a key away from removing that "blank" screen (which is called a frame IIRC). For me, (ctrl-t backspace) remove the current frame. I like the flexibility of Stumpwm where it differentiates between the space taken by an application and where it fits on the screen (Frame) vs the application. The scenario you are describing happens if you have 2 frames while only one app running. Otherwise the next app would just fill that frame that is now available. Personally it doesn't bother me.. I'll just either remove the frame with (ctrl-t-backspace) and then my only app will now be full-screen on that first frame. Or I'll open another app in that empty frame, such as a terminal.
- krispyfi 12y ago
  Thanks for the tip!