phitsc, your suggestion makes sense, and it is an alternative approach that I did actually try, but abandoned.
The only real drawback (if you can call it a drawback, FARR really does an outstanding job as-is) is that
I am actually using the "path" as a command description with complete details, so the user sees something
'fooscript base64.encode' <<<--- FARR launch input box
fooscript base64.encode ;; category: codec ;; this will encode the currently-selected text using base64 encoding <<<--- FARR status bar
That is, the status bar description (aka path) has a long-winded complete description of what the command will do before the user chooses it. This looks great when its down there in the status bar and only showing one-at-a-time when the specific command is highlighted, but it looks not-so-great (aka upside-down awful) when you populate the FARR results window with a bunch of these long-winded descriptions, and you put the short-winded text down in the status bar. The results become very hard to read and poorly aligned.
Incidentally, this option *would* be a great choice if I could get FARR to "clean up" the results window by putting the long-winded descriptions in a *grid* ... where the cells could be aligned and auto-determined by a user-configurable delimiter. (such as pipe or double-semicolon or whatever). That way, the FARR results window would still look clean and easy to use no matter how verbose the individual commands got.
Anyway, I know that the "grid" thing is also a feature that has been already talked about and slated for inclusion in FARR at some point (if time permits).
Another great option would be the ability to copy-paste the the "short winded" text instead of the "long winded" text.
Nonetheless, I'm not complaining, FARR enables so much with what it has, these are really very minor limitations.
Hats off and thanks for the suggestions.