Subj : Exec statement
To   : Fabio Bizzi
From : Kees van Eeten
Date : Fri Nov 08 2019 12:19:56

Hello Fabio!

08 Nov 19 09:46, you wrote to me:

 FB> 08 Nov 19 00:17, you wrote to me:

 FB>>> This doesent work:
 FB>>> exec "/home/husky/bin/netsegments.sh" net33?.???

 FB>>> This always works:
 FB>>> exec "/home/husky/bin/mailin.sh" *.su? *.mo? *.tu? *.we? *.th?
 FB>>> *.fr? *.sa? *.tic *.pkt

 KE>>  Those files have wildcard that includes the full path
 KE>>   */net33?.??? should work as well.

 FB> So the facing asterisk in the working example has a double meaning:

 FB> 1) Every file name before the dot.
 FB> 2) Every path.

 FB> It sounds a bit odd. :) Usually in *nix shells the wildcard limits it
 FB> influence only on the file name and doesn't touch the path.

 It looked strange to me as well. But we are used to use the wildcard in
 a search though directories. In the case of binkd, binkd has the fqn as
 parameter and compares it with the wildcard mask.

Kees

--- GoldED+/LNX 1.1.5--b20180707
 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)

.