Back

@Schneems what comes to mind is doing this within ruby, I believe IRB “is just a class”, so I’d imagine you can write code to coordinate this from within the process.

@eljojo that’s a very unique solution. I’ve not considered it before.

@Schneems been playing with a gist for the past hour. I managed to get the input to work well, but I think now I may need to override `$stdout` https://gist.github.com/eljojo/ddb1257886a5267eab6620d493f61f98

@Schneems I just updated the gist! managed to get it to output `"irb(main):001> 1 + 1\n=> 2\n\n"` into a string

@sstephenson I did that before a long time ago https://github.com/schneems/repl_runner/blob/master/lib/repl_runner/pty_party.rb I think if I moved the reading to a thread and stopped caring if it hung would make things easier.

I also ran into issues where some systems didn’t support PTY in Ruby. IIRC Heroku dynos would support it for a few years. I don’t remember why or if it’s been fixed.

I wish I knew more about the distinction between a PTY and spawning a plain ole process.

@Schneems you sniped me lol. Here’s an expect script that evaluates each argument passed to it with irb:

#!/usr/bin/env expect -f

set prompt "irb.*?> "
spawn -noecho irb --inf-ruby-mode
foreach line $argv {
expect -re $prompt
send "$line\n"
}
expect -re $prompt

———

% ./irb.exp 1+1 "puts 'hi'"
irb(main):001:0> 1+1
2
irb(main):002:0> puts 'hi'
hi
nil
irb(main):003:0>
%

@Schneems just re-read your original toot. Replace `foreach line $argv` with `while {[gets stdin line] != -1}` to read lines from stdin instead

@postmodern I am writing Heroku docs and I want the output to match what customers will see as close as possible via https://github.com/zombocom/rundoc

Your suggestion is a good one, it’s how I drove my tests for background stdin_write. But I don’t want to have to track and sync output styles manually.

I know “script” terminal command is one option for faking a TTY. But the arguments differ between Mac and Linux and that’s important that it works on both for me.