* From: David Wright deb...@lionunicorn.co.uk * Date: Thu, 15 Feb 2018 15:18:45 -0600 > Write …bashrc ; wake ; sleep 5' > and give yourself 5 seconds to read what it says in the xterm.
Interactively. peter@hertz:~$ declare -f wake wake () { input=""; until [[ $input != "" ]]; do echo Beginning loop.; /usr/bin/play /usr/share/sounds/ekiga/ring.wav; read -n 1 -t 4 input; done } Therefore my .bashrc creates wake. Nevertheless, peter@hertz:~$ xterm -display :0 -e bash -c '. ~/.bashrc; declare -f wake; sleep 5' shows a black xterm, which, after 5 s, closes. Appears that this declaration fails. That has become a secondary problem. My current priority is to find why at fails to open the xterm at the specified future time. None of the at documents I've found mention error reporting. Can a failure of at be investigated without changing and recompiling the source? Thanks, ... Peter E. -- 123456789 123456789 123456789 123456789 123456789 123456789 123456789 Tel: +1 360 639 0202 Pender Is.: +1 250 629 3757 http://easthope.ca/Peter.html Bcc: peter at easthope. ca