Re: at based alarm.

2018-02-15 Thread David Wright
On Thu 15 Feb 2018 at 08:19:25 (-0800), pe...@easthope.ca wrote: > * From: Greg Wooledge €wool...@eeg.ccf.org€ > * Date: Tue, 13 Feb 2018 15:01:42 -0500 > > xterm -display :0 -e bash -c '. ~/.bashrc; wake' > > You've lost me. That command is for a wake function rather than > script?

Re: at based alarm.

2018-02-15 Thread Greg Wooledge
On Thu, Feb 15, 2018 at 08:19:25AM -0800, pe...@easthope.ca wrote: > * From: Greg Wooledge > > xterm -display :0 -e bash -c '. ~/.bashrc; wake' > > You've lost me. That command is for a wake function rather than > script? ~/.bashrc is necessary to declare the function before it is >

Re: at based alarm.

2018-02-15 Thread peter
* From: Greg Wooledge wool...@eeg.ccf.org * Date: Tue, 13 Feb 2018 15:01:42 -0500 > xterm -display :0 -e bash -c '. ~/.bashrc; wake' You've lost me. That command is for a wake function rather than script? ~/.bashrc is necessary to declare the function before it is invoked? What

Re: at based alarm.

2018-02-13 Thread Greg Wooledge
On Tue, Feb 13, 2018 at 01:58:50PM -0600, David Wright wrote: > Because .bashrc wasn't called. This might work for a bash function: > > xterm -display :0 -e bash -c . .bashrc ; wake You probably meant: xterm -display :0 -e bash -c '. ~/.bashrc; wake' It would be a lot simpler to put the

Re: at based alarm.

2018-02-13 Thread David Wright
On Tue 13 Feb 2018 at 08:47:56 (-0800), pe...@easthope.ca wrote: > Test the function. > peter@computer:~$ wake > Yes, it works . > > Test the function with xterm. > peter@computer:~$ xterm -e wake > The xterm window opens and immediately closes. A function > is not an acceptable option? > >

Re: at based alarm.

2018-02-13 Thread Greg Wooledge
On Tue, Feb 13, 2018 at 08:47:56AM -0800, pe...@easthope.ca wrote: > peter@computer:~$ cat wake > #!/bin/bash > input="" > until [[ $input != "" ]] ; do > echo Beginning until loop. > /usr/bin/play /home/peter/ring.wav > read -n 1 -t 4 input > done > > Test the script. >

Re: at based alarm.

2018-02-13 Thread peter
From: davidson Date: Sun, 11 Feb 2018 10:31:25 + (UTC) > In the "wake" script, you could start xterm with the -e option (and > put the remainder of your "wake" script in a separate "wake-aux" > script, I guess): OK, thanks. wake is now simplified to this.

Re: at based alarm.

2018-02-11 Thread davidson
On Sat, 10 Feb 2018, pe...@easthope.ca wrote: Given a file named wake containing this script, an alarm can be started with at. at -f wake 6:30 How can the xterm be started with std{in,out,err} connected there? Thanks, ... Peter E. By the way, it looks to me that the shell interpreter

Re: at based alarm.

2018-02-11 Thread davidson
On Sat, 10 Feb 2018, pe...@easthope.ca wrote: Given a file named wake containing this script, an alarm can be started with at. at -f wake 6:30 How can the xterm be started with std{in,out,err} connected there? In the "wake" script, you could start xterm with the -e option (and put the

at based alarm.

2018-02-10 Thread peter
Given a file named wake containing this script, an alarm can be started with at. at -f wake 6:30 How can the xterm be started with std{in,out,err} connected there? Thanks, ... Peter E. #!/bin/sh xterm input="" until [[ $input != "" ]] ; do echo Beginning until loop. /usr/bin/play