Koichi Murase

How about this 1c7f7a1? Could you update ble.sh and check the behavior again?

> that quite confusing with the arguments. Oh, this is something unexpected. It doesn't reproduce in my Linux system. I guess this is related to the man page format used...

@geekscrapy Sorry for the delay. I have added a workaround fa32829. I'm not sure if it really solves the problem in your environment because I don't have macOS. Could you...

Thank you for the report! Currently, it seems I do not experience the problem with Bash 4.4.23. - **Q1** Could you check the behavior for [CHK0004](https://github.com/akinomyoga/ble.sh/wiki/Questions-for-bug-reports#chk0004) and [CHK0005](https://github.com/akinomyoga/ble.sh/wiki/Questions-for-bug-reports#chk0005)? - **Q2**...

I have locally built and tried Bash 4.4.0, but it seems to work with ble.sh in my environment (Fedora 36). On the other hand, I'm not sure if this is...

ping @notmike-5

@notmike-5 Hi, have you already solved the problem? If you are busy, maybe you could just tell me which Linux distribution you have been using when the problem arose so...

@notmike-5 Recently, in #202, we found that some broken timestamps in `~/.bash_history` causes a segmentation fault with Bash 4.4 or lower. I have added a workaround for #202 in commit...

Yes, `ble.sh` needs to scan the entire history when the user has `erasedups` in `HISTCONTROL`. Maybe we can consider processing the duplicate entries using `awk` (when the selected `awk` implementation...

FYI, this is the loop to be optimized: https://github.com/akinomyoga/ble.sh/blob/43be0e4d4fccfcb172a891684878eb65b02cdb2e/src/history.sh#L1382-L1390