<NickH>
I just added that feature in the develop branch.
<NickH>
What do you want to use it for?
<talismanick>
NickH: What you use them for in the script
<NickH>
I may be able to implement it.
<talismanick>
to get back bspwm/sxhkd default behavior of Mod+[ and Mod+] for prev/next tag
<talismanick>
wonderful
<NickH>
I made that script so i could set a binding to go to the next tag
<NickH>
lol
<NickH>
:-)
<NickH>
Was something I missed from awesome.
talismanick has quit [Ping timeout: 250 seconds]
<tleydxdy[m]>
if you selected two tags what would the next tag be?
<NickH>
Both change.
<NickH>
Eg 100100 -> 010010
notzmv has joined #river
<tleydxdy[m]>
hmm
<tleydxdy[m]>
interesting
<NickH>
I think that is how it used to work on awesome. But almost never select more than one tag at a time.
<NickH>
It's also the only sane way that I could think of to do it.
<tleydxdy[m]>
yeah, the only thing that make tags different from workspace is you can select multiple of them
<nor[m]>
No, there is also being able to add a window to multiple tags. That is the even better part to me.
<tleydxdy[m]>
ah yeah, that's also "select" I guess
<tleydxdy[m]>
you get the idea
<NickH>
Also a feature I almost never use!
<NickH>
I think my main use case is accidentally hitting the key bindings for those things and becoming confused!
<NickH>
I keep the keybings in the hope that I will someday start using them :-)
<nor[m]>
I use it constantly. I have no keybindings for set-view-tags and for toggle-focused-tags, I only use set-focused-tags (like Workspaces, only one at a time) and toggle-view-tags (like adding a view to multiple Workspaces).
<tleydxdy[m]>
I usually keep each window with their own tags and select multiple instead
<tleydxdy[m]>
since I normally only want to view stuff on different tags temporarily
Guest54 has joined #river
Guest54 has quit [Client Quit]
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
vaivis has quit [Ping timeout: 276 seconds]
talismanick has joined #river
<talismanick>
Can I get rid of the Xorg drivers (xf86-video-amdgpu, etc) and setxkbmap?
<talismanick>
I have export XKB_DEFAULT_OPTIONS=ctrl:nocaps in ~/.bash_profile
<talismanick>
Do I need xmodmap still?
vaivis has joined #river
<novakane>
talismanick: yes you should be able to remove it all of this
talismanick has quit [Remote host closed the connection]
lxsameer has joined #river
pkap has joined #river
notzmv has quit [Ping timeout: 240 seconds]
vaivis has quit [Read error: Connection reset by peer]
<pkap>
What wlroots branch or commit do I need to build river with session-lock and try out the new waylock?
snakedye has quit [Read error: Connection reset by peer]
<ifreund>
pkap: yep, that's right. I thought I linked in the PR but I guess not
snakedye has joined #river
<pkap>
ifreund: Just looked, you linked it in the PR. I just checked out the branch locally and didn't think to look for PR on github '=D
<leon-p>
pr'd the viewporter patch. Still a draft and untested, but likely mostly done.
<pkap>
The new waylock works well. Is the unlocking a bit faster than with the rust version?
<pkap>
The solarized background is a matter of taste however :D
<leon-p>
pkap: if you like, you can also test the viewporter PR. It should use a lot less memory. Although I am not sure it works yet, since I did not have a chance to setup a river with the lock protocol.
<novakane>
oh nice I see how that works now, indeed that is great to render the whole output
<novakane>
it feels like it would be painful to do with multiple colors though
<novakane>
like with fonts
<pkap>
leon-p: Sure! I have to leave now though, so I'll check it out tomorrow :)
pkap has quit [Quit: Client closed]
<ifreund>
I wouldn't be surprised if new waylock is faster than the old rust version, the rust version is hopelessly abstracted
<ifreund>
and yeah, no configuration yet, I'll probably just implement command line flags for the colors and leave it at that
snakedye_real has joined #river
snakedye_real has quit [Ping timeout: 272 seconds]
snakedye_real has joined #river
snakedye_real has quit [Quit: snakedye_real]
snakedye has quit [Read error: Connection reset by peer]
gwizon has joined #river
gwizon has quit [Quit: leaving]
vaivis has joined #river
snakedye_real has joined #river
elshize has quit [Ping timeout: 272 seconds]
elshize has joined #river
vaivis has quit [Read error: Connection reset by peer]
waleee has joined #river
snakedye_real has quit [Ping timeout: 240 seconds]
lxsameer has quit [Ping timeout: 246 seconds]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
vaivis has quit [Read error: Connection reset by peer]
vaivis has joined #river
mannerism has quit [Ping timeout: 246 seconds]
mannerism has joined #river
<mizzunet>
` float-filter-add app-id|title`
<mizzunet>
How can I get app-id and title of a program from river?