Fish - The friendly interactive shell
Posted May 27, 2005 12:07 UTC (Fri) by
liljencrantz (guest, #28458)
In reply to:
Fish - The friendly interactive shell by diehl
Parent article:
Fish - The friendly interactive shell
The reason fish does what it does right now is that I regularly do things like:
for i in *.c; [...]; end
Inside of shellscripts. I expect this to work even when *.c does not match anything. If *.c is not expanded in this case, this will result in stupid behaviour, unless I add an explicit check, which is clearly dumb.
Maybe the perfect compromise is to have *.c expand to nothing inside of scripts, but emit a syntax error in interactive mode?
(
Log in to post comments)