On Tue, 7 Mar 2017 23:58:40 -0600 "Matthew D. Fuller" <[email protected]> wrote: <snip> > - SortIconManager. This also dates back to twm. Why the heck would > you ever want the icon manager list things out in the random order > it happened to see the windows? That's nutbar. Sorting a dozen > strings takes extra CPU, sure, but hey... This might have something to do with people iconizing (is that a word?), their windows in a certain order, I do did that all the time with KDE's panel because I don't have a enough screen real estate (is there such a thing?). I'd leave it in the code and make it a negative, DontSortIconManager. > And then some that might involve a little more discussion and possibly > user preference, but I still think are decidedly better the other way > around. > > - StartInMapState. This is probably partially as it is for > performance (the map state involves drawing a lot more windows), and > partly because the WSM (in button state) existed before the map > state was added, so having the default this way preserved the > previous behavior. Well, that performance is a non-issue on any > hardware not in a retirement home now. That mostly leaves user > taste. I have no problem believing some people prefer seeing the > labeled buttons to the map, but my gut says the default should be > the other way around. /me Confused What is "Labelled buttons" vs. "map"?
> - RestartPreviousState. Came in with ctwm 2.1. Probably an option to > preserve prior behavior. I think you mostly want ctwm to restart > and pick up where it left off, rather than throwing away your > occupation and even knowledge of what windows were iconified. Does ctwm start your old apps, or is this just if you start them via xinit (before or after ctwm?), or when restarting ctwm, or must you start everything manually? That's a point where the man page is not clear enough. Sincerely, David
