01:50 <FromGitter> <mattrberry> > because ofc you could use overloads on `a` to handle it, otherwise yea guess you just cant use that type in this context ⏎ ⏎ @Blacksmoke16 Not too reduced, no. This is the real example https://github.com/crystal-lang/crystal/pull/12671/files#diff-bc28f7dec142050c0b65d0ca3055ab62f8c3eb9006ed6ab2826ef70ed8eb4abbR272

01:59 <FromGitter> <Blacksmoke16> 👍

13:00 <FromGitter> <noaheverett> Having a interesting issue with running a command with Process.new (or .run) and interacting with it via the input/output pipe (either passed or provided by .run |proc|)

13:01 <FromGitter> <noaheverett> If I run say "bash" and send in "pwd" via input and read the response via output, works great

13:01 <FromGitter> <noaheverett> but I have a specific "daemon" i'm running that generates output and also takes input that it's not taking any input (or at least not visibly responding)

13:02 <FromGitter> <noaheverett> if I set the input pipe to STDIN, it responds to my keyboard input

13:02 <FromGitter> <noaheverett> but if I set it to a custom pipe (i.e. reader,writer = IO.pipe) it doesn't seem to respond

13:04 <FromGitter> <noaheverett> is it possible the command I'm running is just not working correctly with a non-STDIN pipe or any way to debug this in Crystal I may not be thinking of? Tried variations of spawn loops, trying Process.new/Process.run and running with shell and without

13:19 <FromGitter> <noaheverett> Ex: this doesn't respond to input pipe ⏎ ⏎ `````` [https://gitter.im/crystal-lang/crystal?at=635bd6e7f00b697fec6217f5]

13:20 <FromGitter> <noaheverett> ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=635bd70b9ee3ec22b4e408de]

13:21 <FromGitter> <noaheverett> However if I set input to STDIN, it captures my keystrokes and responds, but does not when sending in manually via a pipe

13:21 <FromGitter> <noaheverett> ```code paste, see link``` [https://gitter.im/crystal-lang/crystal?at=635bd75986407c265b939b34]

13:22 <FromGitter> <Blacksmoke16> what happens if you do `input: :inherit`?

13:25 <FromGitter> <noaheverett> @Blacksmoke16 gives error if I try to manually write to proc.input `Unhandled exception: Process#input cannot be nil (NilAssertionError)` but if I remove the manual input command it works with my keyboard input like I had set it to STDIN

13:27 <FromGitter> <Blacksmoke16> try `input: :pipe` then

13:29 <FromGitter> <noaheverett> @Blacksmoke16 in that case, it acts like the first code example and doesn't respond

13:30 <FromGitter> <noaheverett> thank you for your help btw, this is day two on debugging this 🤪 beginning to think maybe the `chs` command just isn't responding correctly to a non STDIN pipe but not for sure

13:34 <FromGitter> <Blacksmoke16> hmm

13:36 <FromGitter> <noaheverett> One other thought, the `chs` command is booting a VM and presenting the Linux login screen console, maybe the input isn't triggering the console "return" key like STDIN keyboard input? I've tried puts (which sends a newline) print with variations of \r or \n

13:40 <FromGitter> <Blacksmoke16> there any flags you need to pass to force it to use input IO when it sees its not a tty?

13:41 <FromGitter> <noaheverett> I'll check into that, I appreciate your help!