How to show command options only with preceding "-"?

[moovinzoo]

For now, when I use command "vim [tab]" git <tab> then auto-complete menu shows files(candidates) and vim command's options.
I guess the options are sourced by man.
But 1. I want inner command to be shown, 2. I don't want command options to be shown without '-'.

I read the discussion here briefly and guess this commit is about my requirement.
But I don't understand how to configure and even cannot sure that code fragment is about this topic.

To clarify, I want the command options only when - is preceding after certain command.
For example,
(1) vim [tab] git <tab> shows only (sub)commands and candidates(files)
(2) vim -[tab] git -<tab> shows only command options

May be super helpful if you could share your knowledge.
Thanks a lot!

FYI. I'm using man-db for man command.

[moovinzoo]

I think this behavior has been changed partially by the timeline below.
My system(arch) originally doesn't have man, I installed vim, git, bash, ble.sh first.
After I installed man and tried configuring blesh with its completion functionality, After I installed bash-completion and found that git is not in the completion list. Now I realize it is so weird. So I tried to reinstall pre-installed packages then bash-completion/completions now listed the completion about that packages. And shows (sub)commands in menu by pressing tab after certain command.

But it is not that consistent. When I use command vim (tab) or git (tab), it shows options, files for the first time when I enters new shell. But when I delete the space before command and re-insert space and press tab then it shows (sub)commands as expected.
So hard to narrow down the reason to me..

[moovinzoo]

Oh, sorry. Yes it was by AUR helper, paru.
I prefer the lts-like version so maybe it was (what I felt feature is quite different from the description) blesh, the old 0.3 one.

[moovinzoo]

OK, as you recommended, I'll keep using manually installed current one.

[moovinzoo]

I temporarily settled down on pretty weird state that not enabling fzf on .bashrc but enable ops in .blerc.
Cannot use ** wildcard in command but all functionality including FZF command like C-R, C-T, A-C are working.
Not showing default menu completion from the beginning gives me comfort.

[akinomyoga]

You seem to have hit a bug of Fzf in the specific version you use, 0.48.1. First, I could reproduce the problem without ble.sh with the following bashrc:

source /usr/share/bash-completion/bash_completion
eval "$(fzf --bash)"
bind 'set show-all-if-ambiguous on'

Then, I checked the difference in the debug trace produced by set -x between Fedora and Arch. It turned out the completion scripts are different. Then, I checked the different versions of fzf. The commit junegunn/fzf@0740ef7 (deployed in 0.48.1) seems to have introduced the bug, and the commit junegunn/fzf@dff8652 (deployed in 0.49.0) seems to have fixed the problem. This is the report upstream: junegunn/fzf#3702.

[moovinzoo]

Sorry for the late replying.

$ paru -Qs fzf
local/fzf 0.48.1-1
    Command-line fuzzy finder

As you mensioned, I installed fzf using paru(AUR helper), and it shows that the exact old version that you said.
I misunderstood that if a package is listed in package manager, it also guarantees that latest(at least close stable) version.
Glad to hear that fzf now solved that integration problem with yours.
Besides sharing the process you narrowing down the reason, was also helpful for me to understand how packages integrates with each other.
Thank you for your great plugin also, I'm enjoying it!

[akinomyoga]

Thanks!

[akinomyoga]

Providing the detailed behavior of the completion settings is not a goal of ble.sh. Instead, ble.sh lets external completion settings to control the behavior.

I guess the options are sourced by man.

Yes. Or, more specifically, the descriptions of the options are retrieved from the man pages. The generation of options for completion depends on the setup. With the plain setup without bash-completion or any other completion settings, ble.sh falls back to the built-in completion generation and uses the man pages to generate options.

But 1. I want inner command to be shown,

Could you explain in a bit more detail what is inner command? If you are talking about subcommands like vim <inner_command>, you need a separate completion setting that provides the list of inner commands. I've checked the completion setting for vim provided by bash-completion, but it doesn't seem to provide completing such inner commands. I checked the man page of Vim, but it doesn't seem to describe any command line usage like vim <inner_command> .... I also searched for "inner command" in Google, but I don't seem to find it. Some people seem to call the inner text objects as "inner command", but these are the commands used in the text editing in the Vim editor and not supposed to be specified to the command line arguments.

2. I don't want command options to be shown without '-'.

This behavior is implemented by bash-completion. You can set it up in your ~/.bashrc (or in /etc/profile.d through the system configuration files such as /etc/bashrc, etc.).

I read the discussion here briefly and guess this commit is about my requirement. But I don't understand how to configure and even cannot sure that code fragment is about this topic.

It is unrelated. That commit introduced a function that users can programmatically get the list of options.

[moovinzoo]

Thanks for your replying. And also sorry for my bad example, vim was not correct for the case, as you said it doesn't have any inner_command.
On behalf of your kind explanation now I could understand generating options or commands are about bash-completion's issue, but unfortunetly, I still can't understand then why behavior of completion menu varies time to time.

As I mensioned early;

When I use command vim (tab) or git (tab), it shows options, files for the first time when I enters new shell. But when I delete the space before command and re-insert space and press tab then it shows (sub)commands as expected.

(vim was not proper example so I'll change the command example to git) when I open the bash shell then typped git <tab> then completion is not working well by showing mene that has only options and files in current directory. When I remove and re-add preceding space after the command, and then completion now works well with showing commands when pressing (tab), actually at last by the second time.

[akinomyoga]

OK, thank you for your clarification!

but unfortunetly, I still can't understand then why behavior of completion menu varies time to time.

Yeah, that is strange, though I don't seem to be able to reproduce the problem. I've replied to the corresponding thread above: #436 (reply in thread).