Skip to content
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

[Bug]: .bash_it/lib/history.bash reuses HISTCONTROL for it's own incorrect purposes by default #2232

Closed
kmcfate opened this issue Nov 22, 2023 · 3 comments

Comments

@kmcfate
Copy link
Contributor

kmcfate commented Nov 22, 2023

Expected behavior

mcfly (a bash history replacement) should properly record and recall commands

Current behavior

mcfly does not properly record or recall commands

Possible solution

Setting HISTCONTROL to 'noauto' fixes the problem, but ignore the fact this is an invalid value for HISTCONTROL. Do not enable .bash_it/lib/history.bash contents by default, or specifically do not run history -a by default as histappend is enabled by default. There is a whole plugin dedicated to bash history, why does this library even exist?

Context

It breaks mcfly

Steps to reproduce

Install mcfly and try to use it.

Bash-it version

36708d7

List of enabled plugins, themes and aliases

N/A

Bash version

5.2.15

Operating system and version

Ubuntu 22.04

bash-it doctor output

# How to get: bash-it doctor

Your ~/.bashrc

# How to get: cat ~/.bashrc

Notes

No response

@cornfeedhobo
Copy link
Member

I would like to see more reasoning than mcfly. We have users that have used this for too many years to leap to this conclusion to accommodate a new tool. I'm still open to reviewing this topic, but I'm sensitive to how central this is to many people's environments and how stable it's been over time.

@kmcfate
Copy link
Contributor Author

kmcfate commented Nov 23, 2023

I've been using mcfly and bash-it for years before this change was introduced. Pulling a recent version broke me. Please see my comments on the PR.

@kmcfate
Copy link
Contributor Author

kmcfate commented Nov 24, 2023

Workaround is adding 'noauto' to HISTCONTROL.

@kmcfate kmcfate closed this as completed Nov 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants