Koichi Murase

@cmm What is your environment? Do you also use Arch linux on WSL?

Thank you so much for the details! > * Those empty values were due to failure to execute `./make_command.sh hash ...` during build-time preprocessing > * That failure in turn...

> (`/usr/bin/env` is unavailable in Nix build sandboxes Ah, OK. I didn't think the shebang `#!/usr/bin/env` would fail (as `#!/usr/bin/env bash` is known as the most portable shebang for Bash)....

> Currently I just include `history -a` in PROMPT_COMMAND. This is sufficient. The reason that I added `history_share` for `history -a; history -c; history -r` is that reloading the entire...

This was discussed in https://github.com/akinomyoga/ble.sh/issues/5#issuecomment-423819663 just after it was first implemented. This is the machine translation of the comment and replies to it: ---- *Translation of https://github.com/akinomyoga/ble.sh/issues/5#issuecomment-423819663 by [@cmplstofB](https://github.com/cmplstofB)* >...

> ``` > ble.sh: insane environment: $USER is empty. ble.sh: modified USER=u0 a516 > ``` This means that the variable `USER` is not set in your environment, which is the...

Discussions are ongoing. - https://github.com/akinomyoga/ble.sh/issues/507 - https://github.com/termux/termux-packages/discussions/23010 - https://github.com/termux/termux-packages/issues/25149

In commit ea1e547bc0ffd39e62a2011b4b4530024d6c91da, I updated the warning message for the Termux environment to make it more precise. I also added a link to the upstream discussion.

This is related to the discussion at https://github.com/scop/bash-completion/discussions/1329#discussioncomment-12163014. I don't think-`/usr/share/bash_completion.d/` is the right directory. It should be somewhere under `/usr/share/bash-completion/` just like the completions for each command is arranged...

> For example in Debian we recently moved most program's own shell completion scripts from /etc/bash_completion.d/ to /usr/share/bash-completion/completions/ > > You can find a list of similar efforts at [uapi-group/specifications#76](https://github.com/uapi-group/specifications/issues/76)...