tdeo has quit [Read error: Connection reset by peer]
tdeo has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
_whitelogger has joined #river
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
dbuckley has quit [Ping timeout: 260 seconds]
dbuckley has joined #river
leon-p has quit [Quit: leaving]
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
keithhub has quit [Quit: WeeChat 3.2]
talismanick has quit [Ping timeout: 268 seconds]
snakedye has quit [Ping timeout: 265 seconds]
notzmv has quit [Ping timeout: 260 seconds]
snakedye has joined #river
waleee has joined #river
novakane has joined #river
notzmv has joined #river
Guest97 has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
Guest97 has quit [Quit: Client closed]
pkap has joined #river
aruhier has quit [Quit: Quitte]
<pkap>
Hi. When using `send-to-output`, the tags stay the same. However, for me it'd be more intuitive if the focused tags of the second output were used.
<pkap>
Ok I see, thanks for the info. It will be interesting to see how this progesses.
<pkap>
But the current way is ok, imho.
<pkap>
Does anybody use yambar with multiple outputs? I have to start yambar separately for each output, is this intentional?
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
pkap66 has joined #river
pkap has quit [Ping timeout: 256 seconds]
pkap66 has left #river [#river]
sillypill has joined #river
<sillypill>
Hey guys! I want to do things like cycle through the tags and toggle between tagmasks
<sillypill>
I had created an issue last year and Leon had suggested I could use zriver_seat_status_v1 protocol to achieve this with the changes here https://github.com/ifreund/river/pull/140
<sillypill>
I think I finally have some time and motivation to write a utility to achieve this, but just wanted to check if somebody here has already managed to do something like this
<sillypill>
Oh and should I wait till v3 to implement these events?
<bfiedler>
There is `focus-previous-tags` and `send-to-previous-tags`, the latter was merged yesterday
<bfiedler>
sillypill:
pedrohlc[m] has joined #river
<sillypill>
Oh wow!
<pedrohlc[m]>
ifreund do you know any magical way to enforce Zig to generate river without BMI2 instructionset? I'm distributing river builds in my repository and this instructions are breaking some users' runtime...
<bfiedler>
zig apparently supports -mcpu
<bfiedler>
so I would imagine something like -mcpu x86_64 or -mcpu amd64 should do it
<ifreund>
pedrohlc[m]: -Dtarget=x86_64-linux-gnu will cause zig to target a baseline x86_64 cpu instead of the exact CPU of the host machine
<ifreund>
-mcpu can be used to tune things more finely
<ifreund>
what repository are you running by the way?
<pedrohlc[m]>
`XBPS_ZIG_TARGET` Pff, wish I had that for pacman
<ifreund>
yup, xbps's template, while far from perfect, are a significant step up over pacman's for anything to do with non x86_64 stuff and cross compilation
<ecocode_>
@ifreund fwiw, I do prefer having tags separated by output. I don't want things I do on one output change stuff I have open on another. So current behavior is excellent to me.
<ifreund>
ecocode_: Nothing's set in stone yet, I think there may very well end up in a place where the current behavior can be emulated without much effort
novakane has quit [Quit: WeeChat 3.2.1]
novakane has joined #river
<ecocode_>
@ifreund that would be awesome :) I love my 2 screens and 18 separated tags.
<ecocode_>
Eventually considering adding another monitor to get even more tags ;)
<bfiedler>
Just don't get 4 monitors, otherwise we have to extend the tag type ;)
novakane has quit [Quit: WeeChat 3.2.1]
novakane has joined #river
<ecocode_>
Lol
<novakane>
those annoying CI failed email notification :/
<bfiedler>
novakane: lol I feel you
<novakane>
bfiedler: you know it's comming but still annoying lol
<snakedye>
bfiedler: challenge accepted 😎
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
elshize has quit [Ping timeout: 265 seconds]
elshize has joined #river
snakedye has quit [Read error: Connection reset by peer]
snakedye has joined #river
snakedye has quit [Ping timeout: 252 seconds]
snakedye has joined #river
snakedye has quit [Ping timeout: 268 seconds]
snakedye has joined #river
sillypill has quit [Quit: Client closed]
snakedye has quit [Ping timeout: 260 seconds]
snakedye has joined #river
novakane has quit [Quit: WeeChat 3.2.1]
novakane has joined #river
snakedye has quit [Ping timeout: 240 seconds]
snakedye has joined #river
leon-p has joined #river
<leon-p>
ecocode_: you know, river has 32 tags per output, so you don't just have 18 separate tags with 2 screens, you have 64 :P
<leon-p>
And it's perfectly possible to use them all as well. F.e. I have bound F{1..9} to access nine additional tags in addition to the common nine. I wonder if I'll ever need it...
leon-p has quit [Ping timeout: 240 seconds]
leon-p has joined #river
novakane has quit [Quit: WeeChat 3.2.1]
kennylevinsen has quit [Remote host closed the connection]
leon-p has quit [Ping timeout: 268 seconds]
leon-p has joined #river
kennylevinsen has joined #river
dbuckley has quit [Ping timeout: 260 seconds]
dbuckley has joined #river
<ecocode_>
@leon-p you learned me something :)
<ecocode_>
On awesomewm I actually scripted creating named tags for each of my projects. when I open a project it created a new tag and populated it with my project-files