2006/1/27, Axel Liljencrantz <[EMAIL PROTECTED]>: > 2006/1/26, Isak Savo <[EMAIL PROTECTED]>: > > 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. > > In this particular case, that can be done. I was thinking about the > general case. For example, on my machine the 'locale -a' command seems > to outputs locale names in the native charset of the locale, which > will sometimes result in invalid strings. What should a command like: > > for i in (locales -a) > ... > end > > do? > > Should it skip the the broken strings. Try to guess what they are? > Skip the broken characters? Maybe the whole command should fail?
Why would you want to skip them? Imagine the following for i in (locales -a) process_string($i); end process_string() might handle, or even depend on, $i being in weird charsets. I'm not familiar with the fish internals, but the logical thing would be to not care unless the string is being printed to the user. Isak PS. I have no idea how other shells handle this. I'm basically arguing theoretical points here :-) ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642 _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
