REPLY: 2:335/364.1 5dc52cbf   
   MSGID: 2:280/5003.4 5dc550f3   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: hpt/lnx 1.9.0-cur 2019-01-08   
   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)   
   SEEN-BY: 1/123 90/1 103/705 154/10 203/0 221/0 1 227/114 229/101 200   
   SEEN-BY: 229/354 426 1014 240/1120 5832 249/307 317 280/464 2000 5003   
   SEEN-BY: 280/5006 5555 292/854 310/31 342/200 396/45 423/120 712/848   
   SEEN-BY: 770/1 2452/250   
   PATH: 280/5003 464 229/426