On 10/18/07, Philip Ganchev <[EMAIL PROTECTED]> wrote:
>
> The trouble is the 'noclobber' option in the shell that shall not be
> named. It makes the '>' operator modal, so when people write '>' they
> expect something different if they are used to having the option set
> than if they are not.
Modality isn't quite as bad as all that, since Fish has the facilities for
excellent just-in-time help. Whenever fish misbehaves for me, it tells me
why, and often exactly where I need to go to figure it out.
# echo foo > bar
Error: file exists, and noclobber is set. Use !> to overwrite the file, or
type help noclobber for more information.
-------------------------------------------------------------------------
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
