We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Run a command like:
echo '1 2 3'
and ash will only record echo '1
echo '1
This happens because read only reads the first line, see
read
advanced-shell-history/shell/bash
Line 136 in e43e312
advanced-shell-history/shell/common
Line 111 in e43e312
advanced-shell-history/shell/zsh
Line 67 in e43e312
I've only tested this in bash, but if zsh's read works the same then it will have the same bug.
The text was updated successfully, but these errors were encountered:
This could be somewhat mitigated in bash with shopt -u cmdhist, which will save each line as a separate command.
shopt -u cmdhist
This could be solved by moving the 'parsing' code to C++/python and doing builtin history 1 | __ash_log --history-from-stdin or something
builtin history 1 | __ash_log --history-from-stdin
Sorry, something went wrong.
No branches or pull requests
Run a command like:
and ash will only record
echo '1
This happens because
read
only reads the first line, seeadvanced-shell-history/shell/bash
Line 136 in e43e312
advanced-shell-history/shell/common
Line 111 in e43e312
advanced-shell-history/shell/zsh
Line 67 in e43e312
I've only tested this in bash, but if zsh's
read
works the same then it will have the same bug.The text was updated successfully, but these errors were encountered: