I'd like to put my vote in for 'noclobber by default'.
That said, I can understand Axel's reticence... > and >> are fundamental
shell features that almost everyone uses frequently. The more you use
something, the more ingrained it becomes, and the harder it is to imagine it
working differently. I myself have never clobbered a file by accident, but I
can see it happening, and I can clearly see where it would be valuable to
avoid.
Personally, I'm in favor of the !> (or >!) syntax (as long as that doesn't
cause parser problems). In several languages the ! is used to indicate
dangerous or destructive commands (the most recent one I recall being ruby),
so it would make semantic sense to me.
Obviously, you'd want a help message to say 'I'm sorry, this file already
exists and is non-zero in length. Use !> to force an overwrite of the file.'
Myrddin
-------------------------------------------------------------------------
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
