-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors and failure from bleopt complete_menu_style
#458
Comments
Can you use
To specify the menu-style You can specify the other menu styles in
Use |
Sorry I didn't mention that I had tried this. I do not see the escape characters like this, but the descriptions are still missing:
Thanks for explaining the difference between the two options. I will use Thanks also for the reminder that I should have been using delayed loading. I tried taking that approach, and now I don't get the 'invalid value' or 'not defined' errors mentioned in the first post, but I still have the missing descriptions shown here. I assumed that I am setting it up incorrectly, but I'm not sure, because it seems to work sometimes, but not others. For example: If I type
If I type
I figured it must be 'pilot error' but when I saw this inconsistency, I had second thoughts. Again, my apologies if this is a bad setup on my behalf. |
Ah, OK. That happens when ble.sh fails to extract the descriptions from the man page. The string
$ ls -lt "$_ble_base_cache/complete.mandb/$LANG" | head One possibility is that the man page of
Another possibility is that the format of the man pages is totally different in your system.
|
I think you are on to the problem immediately. The manpages are installed and seem to be working, but the cache seems incomplete:
I notice
|
I first need to clarify that there is no standard format for the man page for defining the options and their descriptions, so one would need to use heuristic matching to the options and their descriptions (to the text or the source of the man page). ble.sh uses a rather conservative approach so that it doesn't pick wrong strings that just look like options and their description. I confirmed that the options cannot be extracted from the man page of For the
Or another possibility is that the distribution (either mine or yours) modifies the man page, so the format for options and descriptions is different.
I confirmed the behavior in my environment, but this seems to be just because the upstream man page provided by |
OK, it seems like we've fixed everything here, and any further bugs are likely all upstream, so thank you for your help! I'm glad to know that my blesh config appears to be behaving as expected now. Looking at fzf, my version is Anyway, I do understand that it won't be possible to parse every option from every app's manpages perfectly. Honestly, I think it's pretty amazing that ble.sh can get the information that it does! I've seen a lot of very fancy bash scripting in my time, but I think ble.sh might take the cake :D Thanks again for all of your help! |
I checked the behavior in Arch Linux where the fzf version is $ type ble/bin/awk As for the |
Thanks for looking into this for me!
If there is anything I can do to help, you got it! |
I added support for the man-page analysis for the |
As for the This should be caused by the combination of missing escaping of hyphens in the upstream |
I imagine that was very obscure and not trivial to find, well done! |
junegunn/fzf#3885 merged in the upstream. |
I pushed a workaround f160b8f in the |
Thanks! |
ble version:
0.4.0-nightly+365101c
Bash version:
5.2.26(1)-release (x86_64-suse-linux)
Trying to set this option, an error is generated, that the function is undefined. But, it is definitely defined in ble.sh, and can be manually executed.
Either ble-reload, or manually entering the bleopt command exactly as it exists in init.sh, the setting is now accepted without error, however the completion descriptions appear broken:
I guess this is some kind of timing issue? Thanks in advance for any help! :)
The text was updated successfully, but these errors were encountered: