inferior-shell issueshttps://gitlab.common-lisp.net/qitab/inferior-shell/-/issues2023-11-10T17:35:59Zhttps://gitlab.common-lisp.net/qitab/inferior-shell/-/issues/3Recent change broke Quicklisp testing.2023-11-10T17:35:59ZRobert BrownRecent change broke Quicklisp testing.Recent changes on master broke Quicklisp compilation and testing. Failure log is here: http://report.quicklisp.org/2023-11-10/failure-report/inferior-shell.html#inferior-shell_test
I checked out the repo and created a push request to ...Recent changes on master broke Quicklisp compilation and testing. Failure log is here: http://report.quicklisp.org/2023-11-10/failure-report/inferior-shell.html#inferior-shell_test
I checked out the repo and created a push request to fix the problems I found: https://gitlab.common-lisp.net/qitab/inferior-shell/-/merge_requests/1https://gitlab.common-lisp.net/qitab/inferior-shell/-/issues/2`run :output :string/stripped` does not work2023-06-25T14:48:34ZMax S.`run :output :string/stripped` does not workI have tried this command:
```lisp
(inferior-shell:run "ls" :output :string/stripped)
```
It fails with:
```
Invalid UIOP/RUN-PROGRAM:SLURP-INPUT-STREAM destination :STRING/STRIPPED
```
I have checked the source code and the comment ...I have tried this command:
```lisp
(inferior-shell:run "ls" :output :string/stripped)
```
It fails with:
```
Invalid UIOP/RUN-PROGRAM:SLURP-INPUT-STREAM destination :STRING/STRIPPED
```
I have checked the source code and the comment in `run.lisp` gives this example: `:OUTPUT '(:STRING :STRIPPED T)`.
This way it works:
```lisp
(inferior-shell:run "ls" :output '(:string :stripped t))
```
Is this a bug? Or an outdated documentation?
By the way, this diff fixes two typos:
```diff
diff --git a/README.md b/README.md
index 6a7d271..06a0c75 100644
--- a/README.md
+++ b/README.md
@@ -148,15 +148,15 @@ that exports the following macros and functions:
* `RUN/SS CMD &KEY ON-ERROR TIME SHOW HOST`
- `RUN/S` is a shorthand for `RUN :OUTPUT :STRING/STRIPPED`,
- just like a shell's ``cmd`` or `$(cmd)` would do.
+ `RUN/SS` is a shorthand for `RUN :OUTPUT :STRING/STRIPPED`,
+ just like a shell's `cmd` or `$(cmd)` would do.
* `RUN/INTERACTIVE CMD &KEY ON-ERROR TIME SHOW HOST`
`RUN/INTERACTIVE` is a shorthand for `RUN` with `:INPUT` `:OUTPUT` `:ERROR-OUTPUT`
all bound to `:INTERACTIVE`, so you may run commands that interact with users,
- inheritting the stdin, stdout and stderr of the current process.
+ inheriting the stdin, stdout and stderr of the current process.
* `RUN/I CMD &KEY KEYS`
```https://gitlab.common-lisp.net/qitab/inferior-shell/-/issues/1Continually Printing Shell Activity2023-12-20T07:27:58ZAlex PopovContinually Printing Shell ActivityI apologize if this is answered elsewhere or self-evident; I'm only just beginning to learn Lisp.
I'm using `inferior-shell:run` to launch a long-running task which can routinely fail (it's a build validation routine).
My main is...I apologize if this is answered elsewhere or self-evident; I'm only just beginning to learn Lisp.
I'm using `inferior-shell:run` to launch a long-running task which can routinely fail (it's a build validation routine).
My main issue is that I could not find a way of seeing the "live" output of the launched activity.
The reason why I'd like a live-feed is because I could not see the output if an error happened; I looked into the `ON-ERROR:` key, but it yielded little more than saying that there was an exit code of 1. This makes sense, as it seems like this key is a callback to take some kind of recovery action. However, if my task fails, I'd also like to know _why_ it failed, and that's hidden in the output of the command, which does not seem to be accessible.
I tried calling `RUN` like this:
```lisp
(inferior-shell:run (pod-command file) ; this generates a string shell command from the arg FILE
:on-error #'print ; tells me that the exit code was 1
:output *standard-output* ; default, if I understand correctly
:interactive t) ; this was a shot in the dark
```
I'm sorry to ask for free tech support.