Just in case otherds are wondering
On Thu, 29 Jun 2000, Anthony E. Greene wrote:
> Matt Whitfield wrote:
> >
> > DISPLAY=$DISPLAY
> > export DISPLAY
this will work under sh too
>
> Or how about this:
>
> export DISPLAY=$DISPLAY
this will work in bash ans other modern shells, but not sh.
Matt Whitfield wrote:
> Thanks for the prompt reply, but after a few games of UT, a good nights
> sleep and Re-RTM I realised the problem. The man pages clearly states
> that the 'at' command doesn't export the DISPLAY variable when you
> submit the request. I wrongly assumed it exported it at exe
Bret Hughes wrote:
> Probably an X authorization problem. The display is owned by the user logged
> into X and that user must grant authorization to orhers. A quick test would be
> to open up the display to all users with:
> xhost +
> This should generate a message that security has been disabl
Bret Hughes wrote:
>
> Probably an X authorization problem. The display is owned by the user logged
> into X and that user must grant authorization to orhers. A quick test would be
> to open up the display to all users with:
> xhost +
> This should generate a message that security has been disa
Matt Whitfield wrote:
> Hi all, just playing about last night and I set 'at' up as a kind of
> alarm clock, but I couldn't get it to send me an 'Xmessage', it
> complained about not being able to open DISPLAY but if I get it 'echo
> DISPLAY' it does echo the correct one in the email it se
Hi all, just playing about last night and I set 'at' up as a kind of
alarm clock, but I couldn't get it to send me an 'Xmessage', it
complained about not being able to open DISPLAY but if I get it 'echo
DISPLAY' it does echo the correct one in the email it sends me, but
still won't message
