Koichi Murase
Koichi Murase
> Does it employ an implementation method different from standard `bash-completion`? Yes, they are implemented in the following part using the pure ble.sh API for completion (instead of the `complete`...
> A tricky part is that a single Japanese text may have multiple readings depending on the context, I installed the most standard one, MeCab ([mecab-git](https://aur.archlinux.org/packages/mecab-git) and [mecab-ipadic-git](https://aur.archlinux.org/packages/mecab-ipadic-git)), though I...
It's obvious that it's different. `bash-completion` doesn't provide completion for the command name, and the code that I pointed in the previous reply is clearly unrelated to the completion of...
The answer is essentially the same. Even if it is the directory name, the completion of the directory name at that position is not provided by `bash-completion`, so patching `bash-completion`...
I confirmed the behavior. This is not a problem with redrawing, but the last byte `\e` isn't actually processed and pending in the input stream until the next character appears....
Which version of `mcfly` do you use? > Anyway, both Starship (I will be reporting this bug there too) and mcfly do not respect a PROMPT_COMMAND that is an array;...
> ```bash > if [[ ";${PROMPT_COMMAND[*]:-};" != *";_direnv_hook;"* ]]; then > if [[ "$(declare -p PROMPT_COMMAND 2>&1)" == "declare -a"* ]]; then > PROMPT_COMMAND=(_direnv_hook "${PROMPT_COMMAND[@]}") > ``` I think this...
I now remember that when we added the array `PROMPT_COMMAND` to Bash 5.1, we discussed how we do not break the existing Bash configurations that assume `PROMPT_COMMAND` to be scalar....
The discussion is continued from #602.