REPLY: 5898.linux_bb@1:103/705 225b998c   
   MSGID: 1:153/757 5df67bbf   
   CHRS: UTF-8 2   
   TZUTC: -0800   
   TID: hpt/lnx 1.9.0-cur 2019-12-05   
   Hello Richard,   
      
    >> I have never done that and don't know if it's possible. Cron is   
    >> meant to run commands unattended so they are not seen.   
      
    RF> It has been some time since I last did something of this sort, but you   
    RF> should set the proper DISPLAY variable in cron and authorize the cron   
    RF> user to use that display.   
      
   I have never done that. It might be possible, I wouldn't know.   
      
    RF> I think you can do it, but it sounds very fragile to me. Plus, if you   
    RF> don't have a working display by the time cron triggers, it all will   
    RF> crash.   
      
   There is nothing fragile about cron. It just gets stuff done on schedule. There   
    is no way (that I know off) to see what cron is doing but it will go ahead and   
    do what you tell it to do, when you tell it to do it.   
      
    RF> If invoking the scripts from a graphical interface was a must, I would   
    RF> forget about cron and use my desktop environment to load a while loop   
    RF> that called the commands periodically.   
      
   Yes, if you want to see some kind of output cron is not the way.   
      
    Ttyl :-),   
            Al   
      
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)   
   SEEN-BY: 1/123 15/2 57/0 90/1 103/705 153/250 154/10 203/0 220/70   
   SEEN-BY: 221/0 227/114 229/275 354 426 452 616 981 1014 240/5832 249/206   
   SEEN-BY: 249/317 400 250/3 267/800 280/464 5003 292/854 305/2 310/31   
   SEEN-BY: 317/3 322/757 342/200 396/45 423/120 633/280 712/848 770/0   
   SEEN-BY: 770/1 100 330 340 772/0 1 210 500 2452/250   
   PATH: 153/757 250 770/1 280/464 229/426