Thanks for the tip Sepp. I added the following two lines between the 'for'
and 'switch':
echo "argv=" $argv
echo "i=" $i
And get the following output:
argv= --search --contains foo
i= Usage: seq start end {increment}
A quick "which seq" returns "~/bin/seq", which explains the problem.
How does fish resolve functions? Via the PATH?
Thanks for your help!
Peter
On Wed, Oct 1, 2014 at 12:06 PM, Sepp Tannhuber <sepp.tannhu...@yahoo.de>
wrote:
> Perhaps it would help to redefine the history function to print
> $argv[$i] between the `for` and the `switch` statements for debugging.
> First of all, it would be interesting to know which arg fails. Then, the
> question would be why it fails.
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
