Closed cdown closed 1 year ago
Considering all the other things that need to be saved -- mfact, stack position, monitor, etc, this seems a bit useless. A start is in https://github.com/cdown/dwm/tree/cdown/2022-12-16/client_tags though
Hello I've thought of something similar..:
Which is easier to handle than the bits dance done by the dusk knight (impressive, yet confusing/complicated for m):
Thanks! Stuffing them is certainly one option. The only thing I have briefly wondered about is things like a tag or monitor going away after the reload and working out what to do about that, but they can probably just get shoved to monitor 0/tag 0 (and it's pretty unlikely anyway).
Right... I haven't tested that edge case. When a monitor disconnects in the middle of the reload/refresh/restart.
What is even the behavior in vanilla dwm? I would think that all clients over there would go to monitor 0
and first tag (tag 0).
I think it can be implemented a default value if the monitor doesn't exist, but the tag would remain the same, which is better than throwing everything into the first tag imo.
In vanilla on restart everything goes through manage() again, so gets assigned to selmon (or t->mon
for transient windows). Similar for when a monitor gets removed in updategeom().
That also seems like a perfectly fine default if m->num
is nonexistent :-)
Ah yeah, selmon
.
good build btw, very elegant tho I'm not sure how u live without scratchpads.
Thanks! For scratchpad, I have one! It's Mod + Shift + Enter, which opens a floating/centered urxvt client. :)
Just one? haha I got like 5 :p
Hey @cdown off topic, just wondering if you happen to use matrix? Ive seen suckless uses irc but that's not to my liking, not sure what u use.
I use irssi to access IRC, although irssi 1.4 broke a lot of stuff which I need to fix (like nickcolor.pl) :-)
Never really used Matrix, nothing against it, just never had any need to.
I use Mattermost (through matterhorn) for work, but I would definitely not recommend that -- the client is buggy as hell and Haskell does not lend itself well to a program like this.
An idea that could improve selfrestart/etc. Store the current c->tags in an X atom, and read it back out when clients get managed.