<polyrtm>
has anyone else gotten a protocol error when they try to run kile?
<wrkzk>
yeah I did
<wrkzk>
but I gave up trying to get it to work
<wrkzk>
so im not sure what the current situation is
<polyrtm>
maybe I'll open an issue once I unbreak my wm
<polyrtm>
are there any alternatives you're a fan of or just rivertile
<elshize>
polyrtm: https://github.com/riverwm/river/wiki/Community-Layouts if you want something more customizable, might want to give stacktile a try. river-luatile sounds like it would be a good alternative for kile, but I haven't tried it personally.
<polyrtm>
I'll check it out
elshize has quit [Quit: WeeChat 3.5]
polyrtm has quit [Quit: Client closed]
polyrtm has joined #river
polyrtm has quit [Quit: Client closed]
cabal704 has quit [Quit: WeeChat 3.5]
<wrl>
leon-p: well, if stacktile *did*, then that would also solve the issue ;)
elshize has joined #river
waleee has quit [Ping timeout: 260 seconds]
tsraoien has quit [Ping timeout: 246 seconds]
talismanick has joined #river
snakedye has quit [Ping timeout: 260 seconds]
wrkzk has quit [Ping timeout: 246 seconds]
notzmv has quit [Ping timeout: 240 seconds]
fitrh has joined #river
fitrh has quit [Remote host closed the connection]
fitrh has joined #river
mon_aaraj has quit [Ping timeout: 256 seconds]
mon_aaraj has joined #river
simplefinger has joined #river
<simplefinger>
hello! People!
<NickH>
Hey.
<simplefinger>
dnkl: I need a help about Foot term. I have a big monitor (4k) and use wlr-randr for change mode to HD (1920x1080), so foot looks like - https://ibb.co/8dX6gCC Why this happened? In laptop monitor all fine
<simplefinger>
font so small
<NickH>
You set scale factor to 2?
simplefinger has quit [Quit: Client closed]
simplefinger has joined #river
<simplefinger>
>>You set scale factor to 2 Nope
simplefinger has quit [Client Quit]
mon_aaraj has quit [Ping timeout: 272 seconds]
mon_aaraj has joined #river
fitrh has quit [Remote host closed the connection]
simplefinger has joined #river
<simplefinger>
Scaling factor increase all GUI interface.
<simplefinger>
kitty term works well
<simplefinger>
In Sway all fine...
simplefinger has quit [Client Quit]
simplefinger has joined #river
<simplefinger>
fixed. Need remove increasing font from conf files and set scale to laptop and external monitors
simplefinger has quit [Client Quit]
snakedye has joined #river
talismanick has quit [Ping timeout: 276 seconds]
mon_aaraj has quit [Ping timeout: 276 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 246 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
mon_aaraj has quit [Remote host closed the connection]
mon_aaraj has joined #river
mon_aaraj has quit [Ping timeout: 248 seconds]
mon_aaraj has joined #river
<NikhilSingh[m]1>
loginctl lock-session how to make it to perform locking using sway lock?
elshize has quit [Ping timeout: 246 seconds]
elshize has joined #river
waleee has joined #river
<ifreund>
pretty sure swayidle has optional logind integrat
<ifreund>
*integration
<ifreund>
I'd suggest checking out their man page
plumeus has joined #river
<novakane>
plumeus: I saw your message in #zig there is a open PR for input method, feel free to start from here as I am kinda blocked for this and kinda lost a bit of motivation for it
<plumeus>
I had some issues with Matrix so I want to be clear, the first message I can see in this room is the "I saw your message in #zig" one by novakane. Hope I didn't miss anything.
<novakane>
plumeus: yes that the only message, yes that this PR and yes input method protocol is from wlroots :)
<ifreund>
yeah, input-method-unsable-v2.xml is a bit of a special case. It was accidentally merged into wlroots/sway and clients before it was accepted to wayland-protocols
<ifreund>
so wlroots effectively has the cannonical xml
<ifreund>
it's still miles better than v1 though, so it's the best solution at the moment
<ifreund>
input method v3 is proposed for wayland-protocols and will hopefully get merged at some point
Franciman has joined #river
tsraoien has joined #river
cabal704 has joined #river
waleee has quit [Quit: WeeChat 3.5]
waleee has joined #river
wrkzk has joined #river
<xaltsc>
Hey, what's the meaning of each u32 in view_tags ?
<xaltsc>
Why more than one u32 is needed ?
mon_aaraj has quit [Ping timeout: 240 seconds]
mon_aaraj has joined #river
nullndvoid[m] has quit [Quit: You have been kicked for being idle]
mon_aaraj has quit [Ping timeout: 246 seconds]
mon_aaraj has joined #river
waleee has quit [Quit: WeeChat 3.5]
waleee has joined #river
mon_aaraj has quit [Ping timeout: 272 seconds]
mon_aaraj has joined #river
rtypo_bot has joined #river
rtypo_bot has left #river [#river]
<novakane>
xaltsc: an u32 for each views on the output
<xaltsc>
novakane: and the indices correspond through which protocol ?
<novakane>
river send the infos in OutputStatus.zig and a client can get it with river status protocol
mon_aaraj has quit [Ping timeout: 248 seconds]
mon_aaraj has joined #river
<xaltsc>
novakane: I don't understang zig very much, but from what I can tell, there's no way to link the entries of the view_tags array to actual windows. Output{,Status}.zig seem to use the ViewStack which isn't accessible from outside river
<plumeus>
Oh yeah, been meaning to ask since I never really understood. Is it possible to configure certain programs to spawn in certain tags by default, akin to dwm?
<plumeus>
Like, making it so Firefox would always open on the 2nd tag. idk how that would work with multiple monitors.
<novakane>
xaltsc: ah yeah, no you can't have a specific view
<novakane>
plumeus: nope you can't
<plumeus>
Is it a design limitation/choice or just a missing feature?
<xaltsc>
novakane: So what's a use case for this part of the protocol ?
<novakane>
plumeus: a missing feature, probably need to wait for the view management protocol redesign to make this easier to implement