-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds duck-based help50 - don't merge yet #101
base: develop
Are you sure you want to change the base?
Conversation
Works as expected. The only glitch I noticed is that the first error I did after opening a new tab did not trigger the ddb. Perhaps I was too quick?
did also notice that sometimes, the message send to ddb (and shown in the box) has unprintable chars overwriting some of it, like
or
The duck was still able to interpret correctly though. edit to add |
TODOs
txt
, as viacol -b
orsed
[1] Done...
messages when backgrounded process ends, as withset +m
set -e
How to Try
Run:
Run:
Open new terminal and run a command that yields a non-0 exit status (e.g.,
cd foo
)Screenshot
Implementation Details
script
command to capture all stdin/stdout/stderr in a temp file, so that it can optionally be accessed after a command runs.argv
run, fromhistory
$PWD
in which command was run$CODESPACE_VSCODE_FOLDER
in case helpful forcd
, etc.