On Sun, Jan 13, 2008 at 01:31:08PM +0100, Axel Liljencrantz wrote: > I agree with you that giving a nice error message to guide you toward > the fish way of doing things would be nice. In this case, the only way > to do that is to make '!' into a special magical character that has to > be escaped, though, and I don't think that it's worth making yet > another character magical just to give better error messages.
why would it have to be escaped? the !! does not need to be checked until after the command is run. something like a hook funktion that is executed every time after a command is run, and which gets the commandline as an argument (and the exit status) could be a very generic solution which would allow to handle all sorts of failed commands in a custom way. the function could then parse the commandline and output appropriate help messages. as a fish function it would be easely extendible and every user could contribute their favourite. if you add another hook that runs before the command, then someone could even write that sudo filter ;-) greetings, martin. -- cooperative communication with sTeam - caudium, pike, roxen and unix offering: programming, training and administration - anywhere in the world -- pike programmer working in new zealand 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://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Fish-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fish-users
