On Thu, Jun 05, 2008 at 05:54:05PM -0400, Philip Ganchev wrote: > If I recall correctly, the reason > for disallowing execution of variables is that it makes syntax > checking impossible.
that explaind why > $command fails but it doesn't explain the failure of > exec $command there are other commands which work: > watch $command > nohup $command > env $command etc. because they are not builtins, so fish is none the wiser about them. exec could just work the same way. since env just changes the environment for $command if it has some arguments, it can be used as a workaround instead of exec greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix offering: programming, training and administration - anywhere in the world -- pike programmer travelling in china community.gotpike.org unix system- iaeste.(tuwien.ac|or).at open-steam.org administrator caudium.org is.schon.org Martin Bähr http://www.iaeste.or.at/~mbaehr/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
