On Thu, Dec 01, 2016 at 12:26:36PM -0500, Okan Demirmen wrote: > On Thu 2016.12.01 at 17:25 +0100, Erling Westenvik wrote: > > Just a proposal. I like to prevent selected programs (like xclock, > > xbiff, xload) from filling up the taskbar (tint2 in my case) and added a > > while ago a function that lets me set the EWMH flag > > _NET_WM_STATE_SKIP_TASKBAR through a key binding (MS-t). > > Also, since cycling in cwm can get hairy when there are a lot of windows > > open, I added a function that emulates the EWMH flag > > _NET_WM_STATE_SKIP_PAGER and assigned this to a key binding (MS-p) as > > well. > > The latter has proven quite useful for programs that one would want to > > have hanging around - possibly with the sticky/frozen bit set - but > > without interfering with the window cycling flow. > > > > A somewhat crude diff included below for those interested. > > Thanks for the patch. I've been asked about this before and it's on my list, > but you've gotten to it before me - thanks! However, it'd be more interesting > to treat these like we treat 'ignore' today, so that these clients can be > placed in the config and skipped everytime. I haven't yet looked at what > others > wm's do - runtime marking of windows or config-based.
I'd suggest both config-based and runtime marking and will take a stab at config-based marking this weekend. I can see that it may be inapropriate to include this functionality into cwm. The only reason I put it into the source is that I could not achieve the same results with wmctrl(1). (Wmctrl is able to set _NET_WM_STATE_SKIP_PAGER but cwm doesn't seem to honor the atom.) As for other wm's I'm not aware of any that offers exactly this kind of functionality. Perhaps windowmaker or enlightement? But it's not an option for me anyway since I've fallen in love with cwm. > In any case, interested in these, along with a growing list from others too! > > Thanks, > Okan > > > Erling > > > > -- > > Erling Westenvik
