<leon-p>
huh, just found out that if you use chicken scheme, you can compile the scheme program into an executable binary, without loosing the ability to load another scheme file at runtime which can re-define functions and globals
<leon-p>
I wonder if that would be the better choice here over guile
<leon-p>
the main advantage over guile is that on first startup guile byte-compiles the program, which takes a while
<leon-p>
speed-wise they should be reasonably close, since guile is quite well optimized and even JIT's hot bytecode
<leon-p>
but chickens FFi seems more cumbersome...
hush has joined #river
hush has quit [Client Quit]
hush has joined #river
<leon-p>
yeah I think I'll stick with guile for now. if I ever want to switch, all I'd need to do is re-write the bindings and replace one or two guile specific functions, otherwise scheme code seems to be fairly portable between both
Keeto has joined #river
<leon-p>
ok that idea has haunted me the entire bus ride to the lab, so I think I'll also provide chicken binds and try to write the reference WM so that it can be used by both, dammit
<LarstiQ>
leon-p: how long is the bus ride? :)
<leon-p>
~20 minutes, plus the ~5 minutes between two busses I spend at the bakery
<leon-p>
unfortunately, there seems to be no good way to detect which scheme implementation you are running, so unless I am willing to use a preprocessor (ew) I'll probably have to shelf that idea
alexherbo2 has joined #river
Keeto has quit [Ping timeout: 248 seconds]
Keeto has joined #river
<leon-p>
ok, srfi-0 technically allows to detect scheme implementations, but chicken seems way to limited to be used comfortably (no define*, no nested defines, etc.) so I'll wait until r7rs probably before considering that again
Keeto has quit [Ping timeout: 244 seconds]
Keeto has joined #river
Anderson-D has quit [Quit: Connection closed for inactivity]
mtm has quit [Ping timeout: 248 seconds]
mtm has joined #river
hush has quit [Ping timeout: 264 seconds]
Keeto has quit [Ping timeout: 272 seconds]
notzmv has quit [Ping timeout: 248 seconds]
lordmzte9 has joined #river
lordmzte has quit [Ping timeout: 252 seconds]
lordmzte9 is now known as lordmzte
Keeto has joined #river
notzmv has joined #river
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #river
alexherbo2 has quit [Remote host closed the connection]
Guest59 has joined #river
Guest59 has quit [Client Quit]
dani22 has joined #river
<dani22>
Hi, sorry if this is a dumb question or something but.
<dani22>
Is it normal that whenever i try to login into River it just doesn't seem to detect my keyboard or something?? I've tried to use River on a desktop with a bluetooth keyboard and then on a laptop but in both cases River just doesn't seem to detect my input or something :(
<dani22>
It really seems to be an issue coming from River too bc when i use Sway for instance it recognises my keyboard
<leon-p>
In a terminal execute `riverctl list-inputs`
<leon-p>
that will tell you which input devices river knows about
<leon-p>
but I would be /very/ surprised if river missed any that sway handles
<leon-p>
dani22: ^
<dani22>
Oh, let me try that
<leon-p>
(a terminal inside a river instance, of course)
<dani22>
Oh,,, yeah.. about that.. i cant even open a terminal in River 😭
<leon-p>
in that case I suspect your issue is a different one
<leon-p>
input likely works perfectly fine, something else is preventing you from openeing a terminal
<leon-p>
f.e. if you use the provided example configuration, do you have foot installed?
<dani22>
Its not just the terminal, all keybinds just dont work at all :<
<leon-p>
do you actually have any configuration at all for river?
<dani22>
Oh, i dont use foot, i use kitty
<dani22>
And yes, i do
<leon-p>
have you changed rivers config to use kitty?
<dani22>
Mhm :o
<dani22>
Actually let me double check just in case
<leon-p>
honestly I think the example init should probe for what terminal is actually installed rather than hardcoding foot, but that's a different topic
<dani22>
No yeah its supposed to use kitty
<leon-p>
can you upload your config somewhere so I can have a look?
<leon-p>
and if you can, also river debug logs
<ifreund>
try river -c kitty
<dani22>
Sure, where would you like for me to upload it? Or does it not matter :o
<ifreund>
if that opens with a kitty running, the problem is your config
<dani22>
Oh lemme try that too
<ifreund>
bpa.st is good for logs
<dani22>
Oh, river -c kitty worked!
<dani22>
I suppose my problem might really be my config then
<dani22>
Ill try and tweak the config a bit more then and see if i get it to work,,
<dani22>
Ill give an update soon :3
<ifreund>
try running your init script from the kitty running inside river
<leon-p>
if it weren't for the WM protocol, someone should probably write a troubleshooting guide in the wiki
<dani22>
Sorry if this is a dumb question but how do i run my init script in kitty?
<leon-p>
./config/river/init
<ifreund>
your init script should be a executable file
<ifreund>
just type the path to the file into your shell, just like any other executable
pixavi has joined #river
<dani22>
Ohhh that explains alott 😭
<dani22>
I have an executable init and then i have my config which is just a text file for now
<dani22>
Forgot to make it executable
<dani22>
Ah, it worked!
<leon-p>
nice!
<dani22>
I got a ton of errors tho, so i rly just wrote my config wrong,,, but atleast it changed my bg so that means it did work :D
<dani22>
Thank you so much for helping me, im sorry if i bothered much
<leon-p>
no worries
<ifreund>
no problem :)
dani22 has quit [Quit: Ping timeout (120 seconds)]
dani95 has joined #river
dani95 is now known as daniii
daniii has quit [Client Quit]
Keeto has quit [Ping timeout: 246 seconds]
talismanick has joined #river
talismanick is now known as Guest1364
notzmv has quit [Ping timeout: 276 seconds]
catman has quit [Quit: WeeChat 4.5.1]
<leon-p>
ifreund: does river_shell_surfave work with fractional_scale_v1 ?
<ifreund>
leon-p: it should, are you having problems with it?
<leon-p>
not yet, I am ~30min away from testing, but just had a "wait, will this actually works?"-moment
<ifreund>
wlr_scene handles fractional-scale-v1 entirely for us currently
<leon-p>
is the fractional_scale event guaranteed on surface creation? The protocol does not mention anything about that
<ifreund>
no, river will probably send it annoying late currently cause that's what wlr_scene gives us
<ifreund>
*annoyingly
<leon-p>
ah, I think I remember some talk about that in #wlroots
<leon-p>
arguably that guarantee should be added to the protocol, but for now I'll render both on surface creation and on fractional_scale event to be safe
<leon-p>
worst case the widget will be blurry for a frame or two, its size shouldn't jitter, so everything is fine
<ifreund>
I mean, river won't know what scale to use until it knows where the surface is positioned by the wm
<leon-p>
the wm protocol could require shell_surfaces nodes to be positioned before first surface commit
<ifreund>
true
catman has joined #river
catman has quit [Quit: WeeChat 4.5.1]
catman has joined #river
<leon-p>
it works
<leon-p>
nice
<leon-p>
~1k LoC and a few hours of thinking to get a red rectangle, lol