<cbb>
I have some suspicions of what might be happening, but I need to look into it more
<dnkl>
hmm, alright... so perhaps move the setsid-call, and start double-forking new terminal instances?
<cbb>
dnkl: I'm thinking there could be a window of time where foot itself has a controlling terminal and processes that lose their controlling terminal get sent SIGHUP by the kernel
<cbb>
it's just a suspicion at the moment though
<cbb>
the POSIX spec pages for close() and _Exit() might be of interest
<dnkl>
we ignore SIGHUP very early in main.c. I _think_ we don't reset it, in the child process, until after calling setsid
hmht has quit [Ping timeout: 256 seconds]
cbb has quit [Quit: WeeChat 4.2.1]
cbb has joined #foot
<cbb>
dnkl: oh maybe that isn't it then
<cbb>
I haven't had chance to properly look at the code yet
qyliss has quit [Quit: bye]
qyliss has joined #foot
Altomon has joined #foot
cbb has quit [Quit: WeeChat 4.2.1]
cbb has joined #foot
Altomon has quit [Remote host closed the connection]
newchair has joined #foot
newchair has quit [Client Quit]
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
alexherbo2 has joined #foot
alexherbo2 has quit [Remote host closed the connection]
bgs has joined #foot
bookworm has quit [Ping timeout: 260 seconds]
cbb has quit [Quit: WeeChat 4.2.1]
newchair has joined #foot
bookworm has joined #foot
ttyyls has quit [Remote host closed the connection]