<leon-p>
would be kinda cool if the terminals padding changed colour based on the content of neighboring cells. Right now it looks a bit silly when you have a TUI program with a background colour different then your terminal colourschemes background.
<leon-p>
have we already fixed the bug where a new layer surface only get's pointer focus when the cursor is moved? I "discovered" it just now, but it seems familiar and I am on an old version
<ifreund>
it kinda stopped being useful at some point, now we just have separate issues for specific things
<icp>
yes that one
<icp>
Is a scene graph implementation planned?
<novakane>
what's position independent executable?
<ifreund>
icp: yes, definitely. I just haven't found time to do the work to make it happen yet
<ifreund>
it's a pretty big chunk of work that only I can really do, if someone else did it it would be just as much effor to review as to do it myself
<icp>
(y)
<ifreund>
novakane: the generated code uses only relative addresses so that it can be executed at any arbitrary place in memory
<ifreund>
it enables security hardening stuff involving randomizing the address space in which a binary is run
<ifreund>
lots of distros enable it by default these days
<novakane>
oh ok sounds nice, is that something everyone can use or you need some specific setup?
<ifreund>
novakane: just need to build with `-Dpie` and the linux kernel does the rest afaik
<tleydxdy[m]>
the flag is automatically enabled when you have your computer upside down
<Shinyzenith[m]>
-Drelease-safe and stripping was removed from river-git
<Shinyzenith[m]>
which is what I'm on currently
<novakane>
so looking a bit around it seems like PIE can cause some performance issue, mainly on 32-bit x86 arch, though can't really find any real benchmark for this
<leon-p>
Shinyzenith[m]: still no debug info. There should be no question marks here: ???:?:?: 0x233b14 in ??? (???)
<ifreund>
yeah, perhaps you didn't start a new river session after rebuilding the package?
<ifreund>
you could also try to reproduce under gdb running in a nested session
notzmv has quit [Ping timeout: 260 seconds]
<Shinyzenith[m]>
<leon-p> "Shinyzenith: still no debug info..." <- Hmm then what am I doing wrong?
<Shinyzenith[m]>
<ifreund> "yeah, perhaps you didn't start a..." <- I did actually
<Shinyzenith[m]>
<ifreund> "you could also try to reproduce..." <- Already thought of that but the crash is too inconsistent to have it constantly run under gdb
<tiosgz`>
try adding 'debug' to the options array in the PKGBUILD. not sure if that changes anything, but sway-git uses that
<ifreund>
Shinyzenith[m]: wait, you're on arch right? do you know how to use coredumpctl?
<Shinyzenith[m]>
I'm on artix so no systemd-coredumpd
<Shinyzenith[m]>
s/coredumpd/coredump/
<ifreund>
have you configured your system to enable coredumps?
<Shinyzenith[m]>
tiosgz`: Hm pretty sure that won't do much for river
<Shinyzenith[m]>
ifreund: I don't think so, I normally just check dmesg for segfaults
<tiosgz`>
i use `prlimit -c104857600: river` fwiw (to start river w/ coredump enabled)
<ifreund>
poking at a coredump with gdb would be more reliable than zig's builtin stack trace dumping
<Shinyzenith[m]>
On second thoughts I have been running my pc for like 9 hours now
<Shinyzenith[m]>
I should try a fresh reboot just to make sure everything works because I did a couple updates while running
<Shinyzenith[m]>
ifreund: OK I will try to set that up
waleee has joined #river
vermi has quit [Ping timeout: 246 seconds]
icp has joined #river
<icp>
after booting into new 1.3 all my hotkeys seem broken - mod4 is now Super apparently