Currently `builtin -n' and `functions -n' print their ouput one entry per line:
fish> builtin -n read bg break case builtin cd complete eval for or set fg continue return switch bind random status ulimit while not exec begin functions jobs function command and exit end . if else commandline This wastes lots of creen space, and may even scroll past the screen. Is there a good reason to do that? I prefer to see them on the same line: fish> builtin -n read bg break case builtin cd complete eval for or set fg continue return switch bind random status ulimit while not exec begin functions jobs function commandline fish> Disagreements? Philip ------------------------------------------------------- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
