Koichi Murase
Koichi Murase
I'm still unsure about whether the provided reasons make sense. If a distribution want to put the compat directory in another location, the distribution can always set `BASH_COMPLETION_COMPAT_DIR` when loading...
> Having to do local patches or modifications is strictly worse than simply fixing the behaviour for everyone out of the box. Everyone needs to notice, know and ship the...
This PR has been full of deception from beginning to end, and the OP has finally rage-quitted. They pretended to be authoritative and tried to force us to follow them,...
To clarify first, I didn't reject the suggestion, though the OP seems to claim in the UAPI thread that we've rejected it. From the provided information, I couldn't judge whether...
I've corrected the PR title, reflecting the actual change of the current version. The first commit has been merged in #1447.
After that, I found the page "[Configuration Files Specification | UAPI Group Specifications](https://uapi-group.org/specifications/specs/configuration_files_specification/)" in the UAPI repository by myself, and it told me the details that hadn't been revealed or...
That is what the disclaimer means. > *From README* > > Q. I author/maintain package X and would like to maintain my own completion code for this package. Where should...
This typically happens when `set -o posix` is set, but the problem doesn't arise with my environment (which is not VS Code or kitty). - **Q1**: What are the result...
- **Q1**: What is the result of the following command? ```bash $ builtin trap ``` > So this is expected behavior then I assume, and one should disable `posix` when...
OK, so the `DEBUG` trap is present in your setup, and the trap string set by `ble.sh` is called through the `DEBUG` trap even in the user-command context. I could...