On Oct 19, 2007, at 4:01 AM, Beni Cherniavsky wrote: > > Sadly, the above scripts breakage scenario is bound to occur once now, > if we change the definition of ">". But in the long term, we will be > better off after the change.
I'd like to cast my vote for not changing the ">" semantics. There's something to be said for staying somewhat consistent with what other shells do. While those of us who use fish daily and have it installed on all of our machines will be able to pick up the new semantics quickly, new users may be unpleasantly surprised when ">" fails to overwrite a file. Just my $0.02. -Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
