On 1/17/06, Philip Ganchev <[EMAIL PROTECTED]> wrote: > Functions defined without a description are printed with the > definition body as a description: > > fish> function foo; echo hello; end > fish> functions foo > function foo --description echo\ hello\; > echo hello; > end > > fish> functions -d "" foo > fish> functions foo > function foo > echo hello; > end > > fish> > > I'm sure this is not the intended behavior.
Actually it is. I find it to be an ocasionally useful for short functions with no description - you get to see what the function does as a description. > > It would seem from the above that the bug is in `function', but I > don't see any modifications of builtin_function() since version 1.18.2 > that could cause this. > Fish has always behaved this way. Perhaps this behaviour should be limited to shorter functions, but I do find that it is more usefull than to simply use 'Function' as the description. -- Axel ------------------------------------------------------- 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
