groknull has quit [Remote host closed the connection]
MyNetAz has quit [Remote host closed the connection]
elshize has joined #river
MyNetAz has joined #river
elshize has quit [Ping timeout: 244 seconds]
groknull has joined #river
groknull has quit [Remote host closed the connection]
groknull has joined #river
groknull has quit [Remote host closed the connection]
Guest50 has joined #river
Guest50 has quit [Quit: Client closed]
adamcstephens has quit [Remote host closed the connection]
adamcstephens has joined #river
i01011001 has joined #river
<i01011001>
is there a way to focus-view directly to master
<Nickli>
that's the zoom command iirc
<i01011001>
i meant change the focus to the current master not change the focused slave to master
<Nickli>
hmm, doesnt ring a bell
<Nickli>
might be one of the actions that isnt in yet, not sure
<i01011001>
seems like it
<leon-p>
(for future reference, the canonical names in river are "window stack", "main area" and "remainder area" or "secondary area")
<i01011001>
I"ll keep that in mind..
<Nickli>
i get what you'r saying... but looking closer at what's written it is confusing
<Nickli>
Main/WindowStack is self evident
<Nickli>
are the other two different names for the Stack?
<leon-p>
the stack is the entire thing, including both what is in the main area and the rest
<Nickli>
right, all windows are arranged in a stack from number "1" and onwards
<larstiq>
now I'm not sure if you mean to exclude 0 or are starting at 1?
<Nickli>
so it's Main and Secondary/Remainder area
<leon-p>
yes, always has been
<Nickli>
larstiq, were debating internally on wether to say 0 or 1, so i went with thinkg First window
<leon-p>
you can't do indexing right 🤷 whether you start at 1 or 0 is just a philosophical difference
<larstiq>
I'd argue 0 is handier for offset math, but then I got an off-by-one area in today's aoc so :shrug:
<larstiq>
exciting reading about rwm in the backlog!
chooky has joined #river
<chooky>
Does river support the input-method-unstable-v2 and virtual-keyboard-unstable-v1 protocols? I couldn't see this info in the readme or the wiki
<vyivel>
chooky: based on quick grepping, it does
<vyivel>
generally, you can run wayland-info and check what globals are exposed
<chooky>
vyivel: the codebase or the readme? i'd feel stupid if it was in the readme haha
<vyivel>
the codebase
<chooky>
something like `wayland-info | grep "input-method-unstable-v2" should show something?
<vyivel>
the global name is zwp_input_method_manager_v2
<chooky>
ah okay, thanks for that
<chooky>
vyivel: any idea why https://github.com/mswiger/seogi wouldn't be working on chrome then? even when launching with `google-chrome --gtk-version=4 --ozone-platform-hint=auto --enable-wayland-ime`
<chooky>
it seems to work fine for foot, kitty, firefox, etc
<vyivel>
chooky: chrome uses text-input-v1 instead of text-input-v3 which is the protocol for compositor to relay high-level text input events to clients with
<vyivel>
(-v1 is not implemented by wlroots and river)
<chooky>
:sob: I see... is there no way of working around this then. chrome is simply being painful as always
<vyivel>
although there was a flag added recently to use -v3 in chromium i think?
<chooky>
I guess to bring this into context, i don't really care for getting the IME working with chrome but more or less vesktop (a linux discord app) which supposedly - "Vesktop is an Electron app, which is Chromium based"
<chooky>
I guess the next step would be to check the electron docs and see if they support v3?
<vyivel>
if chromium doesn't electron definitely doesn't
<chooky>
> if chromium doesn't electron definitely doesn't
<chooky>
right, i was more or less thinking in regards to the -v3 flag you mentioned
<chooky>
thanks for the link to the issue. i'll take a read through now
i01011001 has quit [Ping timeout: 240 seconds]
<vyivel>
basically the solution here is to wait for chromium to support v3 (which might include some protocol additions first afaict), then for electron to get those changes too, then for electron-based programs to update
<vyivel>
alternatively if you're willing to write some zig, patch river to add text-input-v1 support
<chooky>
I write most my personal projects in zig, so that's not the issue. it's my lack of knowledge into the protocols. i guess i could do some digging into this stuff and see how difficult of a task it could be. unsure what your expertise is with these things but would you happen to know any nice places to start learning / reading about implementations
<chooky>
and workings of these things?
<vyivel>
you can take a look at wlroots text-input-v3 implementation
<vyivel>
i imagine -v1 and -v3 are not *that* different after all
<vyivel>
i've written a bunch of wayland protocol impls but not a single line in zig so dunno about potential language-specific problems that may arise
<chooky>
> you can take a look at wlroots text-input-v3 implementation
<ifreund>
tldr; nope, but you will be able to do it yourself eventually
<sewn>
is there a blog or some changelog of river I can read
<ifreund>
I mean, I have have a blog where I post about river once a year or so
<sewn>
awh once a year
<ifreund>
I may or may not post about river more frequently on mastodon
<ifreund>
the commit log is the only real changelog
<larstiq>
the commit messages are pretty good to get a sense of what's happening
<ifreund>
the release notes generally summarize the major changes, but don't cover anything that's happened since the last release of course
<leon-p>
I don't think I could write a monthly river blog even if I wanted to, things float down the stream quietly, i.e. thingss do happen, but not at a pace or volume that anyone could editorialize into relevant writing of that frequency