On Fri, May 22, 2015 at 03:29:38PM -0400, Greg Reagle wrote: > On Fri, May 22, 2015, at 02:26 PM, Greg Reagle wrote: > > Hello. I would like dvtm to behave differently. I don't want creating > > a new shell window (Mod-c) to make the new shell window the master; I > > want the master to stay the master. I also don't want creating a new > > shell window to renumber all the windows; I want the new window to be > > one plus the last window number. > > > > I have started to work on this, and it seems that adding the new window > > to the end of the window list rather than the beginning will achieve > > these two goals. > > > > Has anyone already implemented this functionality? Does the way I'm > > suggesting make sense? > > So here is my attempt. It compiles and works pretty well. It has one > issue that I think might be a problem though. In the window numbering, > the visible windows can be in a state where they are not continuous > (e.g. window 3 might be minimized and windows 1,2,4 might be visible). > > Any thoughts? Thanks.
I don't think this should be mainline workflow, but it probably makes a nice patch. However, you should understand that window numbering is always the same with the master being window #1 and the rest in consecutive order. The clients are then arranged within those pre-numbered windows, The clients can move around to different window positions, but the window numbers stay the same. When you minimize a window, it takes its client with it and moves to the end of the stack. When you unminimize a window, it pops up to the master (#1), bringing its client along, and pushes the other clients down the stack. -Ross
