The readme uses history so surely the author knows this?
function preexec_go() {
local command_line=$(history 1 | sed 's/^ *[0-9]* *//')
if [[ -n "$command_line" && "$command_line" != "preexec_go" ]]; then
# CHANGE THIS PATH to the location of your 'envoy' executable
(
~/Desktop/projects/envoy/envoy "$command_line" >/dev/null 2>&1 & ) disown
fi
}
trap 'preexec_go' DEBUG
I think the point isn't what the author knows or does not know but rather a question for the rest of us - what does this tool offer that bash history doesn't?
The list of features on the Github page doesn't provide an answer:
- Starts and stops on demand: Only logs commands when you explicitly turn it on.
- Saves to a custom file: You can specify the log file name.
- Cross-platform: Works on both Linux and macOS using bash or zsh.
- Minimal overhead: Runs in the background and has no noticeable impact on shell performance.
Bash largely covers all of those too.
...is this program just copying lines from shell history inti a different file?