On 1/12/06, Philip Ganchev <[EMAIL PROTECTED]> wrote: > 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?
That's not good for scripts that want a quick and easy way to list all functions. Currently you can do something like: for i in (builtin -n); echo $i; end The proper thing is to behave like ls, i.e. one-per-line only if stdout is not a terminal. I'll change this. > > Philip -- 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://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
