Re. Re: [Fish-users] Problem using -exec paramter on find

[ray hammond]

Thanks, is that a conscious decision for fish to operate that way? I like the concept of fish and it would be great if shell would support this command, minus the quotes, for cross-shell compatibility.  I have commands similar to this in several shell scripts, across several systems, hence changing each to include the quotes would be a bit of a headache.     >On Sunday 16 April 2006 12:51, ray h wrote: >> I running suse 10 OSS, I have experienced a problem using the find command >> below >>  >> find . -mtime +1 -exec file {} \; >>  >> Using a bash or csh shell I get the following results: >>  >> ./access_log: ASCII text >> ./rc.out: ASCII English text >> ./error_log: ASCII text >>  >>  >> Using fish, version 1.21.4, I get the following: >>  >> cannot open `' (No such file or directory) >> cannot open `' (No such file or directory) >> cannot open `' (No such file or directory) >>  >> What am I doing wrong, or is this a problem with fish? >  >Try putting {} in quotes: '{}'