Describe the bug
See: #501 for additional context. I believe that #501 should be re-opened, as the fixes mentioned in it are incomplete.
TL;DR: When Copilot executes a Bash command, it truncates the user's ~/.bash_history, ignoring the user's HISTFILESIZE. This is a consequence of the manner in which Bash is invoked (an interactive shell spawned with bash --norc --noprofile)
Affected version
v1.0.11
Steps to reproduce the behavior
- Observe
wc -l ~/.bash_history
- Instruct copilot to run a Bash command
- Observe
wc -l ~/.bash_history
Expected behavior
Copilot does not modify ~/.bash_history in any way, especially not truncation.
Additional context
This issue can be worked around by adding the following shim to your ~/.bashrc.
copilot() {
HISTFILE=/dev/null command copilot "$@"
}
Describe the bug
See: #501 for additional context. I believe that #501 should be re-opened, as the fixes mentioned in it are incomplete.
TL;DR: When Copilot executes a Bash command, it truncates the user's
~/.bash_history, ignoring the user'sHISTFILESIZE. This is a consequence of the manner in which Bash is invoked (an interactive shell spawned withbash --norc --noprofile)Affected version
v1.0.11
Steps to reproduce the behavior
wc -l ~/.bash_historywc -l ~/.bash_historyExpected behavior
Copilot does not modify
~/.bash_historyin any way, especially not truncation.Additional context
This issue can be worked around by adding the following shim to your
~/.bashrc.