> 
> I don't have a machine with wayland, so I can not try out fuzzel
> itself. I tried your program with "dmenu" instead, and, after
> swapping the close-input-port/close-output port uses, it seems
> to work. 
> 

Oh man, how stupid I feel now… This was also the advice of Peter Bex sooner 
(sorry to not have react to it before :/). I was pretty sure to have tested 
that sooner in my iterations, and I remember receiving an error such as "xxxx 
is not an output-port" or something like that, and nothing when using the 
opposite. That’s why I organize my code like this, thinking from the subprocess 
point of view (instead of the current caller). However I probably did something 
else wrong at the time because now, just swapping the two calls… everything 
works as expected. By digging inside the fuzzel code, I understand that if 
stdin is not closed, then it places itself in some sort of pending mode, in 
case other stuff come in… hence my "frozen" feeling.

If I try hard to remember, I probably confused myself by trying to play with 
processes, which does not open stdin (or close it already on their side), hence 
the error message I remember. Anyway, now it’s clearer for me.

So sorry for the time lost and thank you very much for your help both of you!

Have a great day!




Reply via email to