Input support in general

[jcguu95]

Does cmd support interactive input?

1

For example, (cmd "/tmp/test.bash") does not prompt the user to enter a value, where tmp/test.bash is

#!/bin/bash

read x; echo "$x"; exit;

We can give it a string as input, but that isn't interactive enough if the end goal is to replace shells.

2

Another example arises when the system tries to read a password. For example,

CL> (cmd:cmd "sudo echo a")
sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

Using -S doesn't work either as the repl does not try to read a password.

[ruricolist]

There's no special support at the moment, but you can provide cmd with a stream as input:

(with-input-from-string (in "hello")
    (cmd:cmd "~/tmp/test.bash" :< in))

If you want a prompt you can use read-line:

(with-input-from-string (in (read-line))
    (cmd:cmd "~/tmp/test.bash" :< in))

It might be worth adding a :<<< parameter to simplify this.

[ruricolist]

Here strings are supported as of 38cb13d.

[jcguu95]

Thanks for the patch! It's closer to the general (namely, fully interactive) case :)

Related: joaotavora/sly#448

[vindarel]

Hi, I was looking for sudo, and it's working with uiop:run-program:

(uiop:run-program '("sudo" "htop") :output :interactive :input :interactive)

(note the use of the visual htop command, works fine too). Could not find a cmd equivalent. (edit) => use :input :interactive :output :interactive.

(edit)

For example, (cmd "/tmp/test.bash") does not prompt the user to enter a value, where tmp/test.bash is […]

it works too with (cmd:cmd "./test.bash" :input :interactive :output :interactive)