3 ms·

Playing around with a bit more, I think the tool might not be suitable for my use cases. If I try it with the command `gcc -Wall` it thinks that each of W, a, l

Playing around with a bit more, I think the tool might not be suitable for my use cases. If I try it with the command `gcc -Wall` it thinks that each of W, a, l, (and l), are separate single-character arguments, and therefore fails badly: ``` > gcc -Wall -W Unknown flag -a Unknown flag -l Search the library named library when linking. (The second alternative with the library as a separate argument is only for POSIX compliance and is not recom... ``` Additionally, it is really slow, I suppose because gcc has a huge man page? It is really useful for lots of small commands like ls and find, and things where I often forget parameters. Maybe it could be changed so that I can whitelist only certain commands to trigger the hints?

elcapitan 9mo ago
Or it could cache the parsed manpages or reuse the information that fish already extracts from there for autocompletion?
- behnamoh 9mo ago
  I do use caching on the first trigger of a flag. Maybe I'll add a comprehensive manpage "reading" on the first install to speed things up.
  - elcapitan 9mo ago
    That makes sense, or something like `fish_update_completions` that you can call explicitly.
    - behnamoh 9mo ago
      That also makes sense! I'll think of a good strategy based on these comments and push to main.
esseph 9mo ago
From the website: Known Limitations Some commands with unusual man page formats may not parse correctly Commands that open interactive help (like git commit --help opening a pager) require man page fallback Combined short flags like -rf are split into individual flags