I partly know what's going on over here with when files I try to create.
It's possible the monitor is off though it's attached. I'll try
cycling the monitor and repeating this file creation and see if I get a
DISPLAY value saved. Not having vision I don't always have a good idea
whether the monitor is turned on or not.
On Fri, 22 Dec 2017, john doe wrote:
Date: Fri, 22 Dec 2017 11:46:12
From: john doe <johndoe65...@mail.com>
To: debian-accessibility@lists.debian.org
Subject: Re: xclip problem
Resent-Date: Fri, 22 Dec 2017 16:46:29 +0000 (UTC)
Resent-From: debian-accessibility@lists.debian.org
On 12/22/2017 5:24 PM, Jude DaShiell wrote:
No, I used the ">" operator when I ran the command.
If you do '> dn.txt' in the current directory, 'dn.txt' is created in the
current directory.
$ > dn.txt
$ ls
dn.txt
$ jkjsiuu > dn.txt
-bash: jkjsiuu: command not found
$ ls
dn.txt
The file 'dn.txt' is created regardless of the command before it.
You could try:
<COMMAND> 2>&1 > /fully/qualified/path/dn.txt
'echo $DISPLAY > dn.txt' -- The file dn.txt is created in the current
directory.
On Fri, 22 Dec 2017, john doe wrote:
Date: Fri, 22 Dec 2017 11:14:47
From: john doe <johndoe65...@mail.com>
To: debian-accessibility@lists.debian.org
Subject: Re: xclip problem
Resent-Date: Fri, 22 Dec 2017 16:15:05 +0000 (UTC)
Resent-From: debian-accessibility@lists.debian.org
On 12/22/2017 2:44 PM, Jude DaShiell wrote:
?I just checked for dn.txt after running updatedb as root using locate
and
?no results got returned.? The file was not produced.
The redirection operator '>' creates the file 'dn.txt'.
It looks like that command was never executed.?
With out having the all conversation, the fact that DISPLAY is not
populated might be the real issue here.
--
