Crap, forgot to hit "reply all" :-/ ---------- Forwarded message ---------- From: Isak Savo <[EMAIL PROTECTED]> Date: 2006-jan-26 19:52 Subject: Re: [Fish-users] Completion bug To: Axel Liljencrantz <[EMAIL PROTECTED]>
2006/1/26, Axel Liljencrantz <[EMAIL PROTECTED]>: > 2006/1/26, Philip Ganchev <[EMAIL PROTECTED]>: > Also, I'd be interested to hear peoples opinions on what fish should > do when a command substitution returns invalid output. Right now, the > whole line is discarded and an error message is printed. Some > alternatives: > > * The entire command substitution fails, either with or without a warning > * Silently skip bad lines, either with or without a warning (This is > the current bahaviour, with the warning) > * Ignore only the 'broken' character, either with or without a warning > * Try using a fallback character set, either with or without a warning > (I hate to admit it, but which set to use should probably be user > configurable) Just display the name of the command without description.. It's far more important to know that the command exists than the description of it. Something like this: $ ls<TAB> ls (List contents of directory) lsfoo (<<No description found>>) lspci (List all PCI devices) ... Perhaps the "No description found" part could be error colored or something. It could also be completely omitted, leaving just an empty parenthesis. Just my .02€ Isak -- Isak
