Re: xclip problem

2017-12-22 Thread john doe
On 12/23/2017 5:32 AM, john doe wrote: On 12/22/2017 9:38 PM, Jude DaShiell wrote: I tried all of this in a terminal and got :0.0 for the DISPLAY value. So I exported DISPLAY=:0.0 then ran xclip and xclip errored out because it couldn't find DISPLAY :0.0. From: https://github.com/astrand/x

Re: xclip problem

2017-12-22 Thread john doe
On 12/22/2017 9:38 PM, Jude DaShiell wrote: I tried all of this in a terminal and got :0.0 for the DISPLAY value. So I exported DISPLAY=:0.0 then ran xclip and xclip errored out because it couldn't find DISPLAY :0.0. From: https://github.com/astrand/xclip "* Connects to the X display in $D

Re: xclip problem

2017-12-22 Thread Jude DaShiell
Interesting quotes around the whole echo command, I'll try that and see what happens. On Fri, 22 Dec 2017, Paul Gevers wrote: Date: Fri, 22 Dec 2017 14:07:51 From: Paul Gevers To: debian-accessibility@lists.debian.org Subject: Re: xclip problem Hi Jude, On 22-12-17 20:04, Jude DaShiell wrot

Re: xclip problem

2017-12-22 Thread Jude DaShiell
I tried all of this in a terminal and got :0.0 for the DISPLAY value. So I exported DISPLAY=:0.0 then ran xclip and xclip errored out because it couldn't find DISPLAY :0.0. On Fri, 22 Dec 2017, john doe wrote: Date: Fri, 22 Dec 2017 14:29:42 From: john doe To: debian-accessibility@lists.debi

Re: xclip problem

2017-12-22 Thread john doe
On 12/22/2017 7:56 PM, Paul Gevers wrote: Hi Jude, On 22-12-17 19:26, Jude DaShiell wrote: as near as I can tell, echo does not work when used after alt-f2 in a text command. Just tried, for me it works (in KDE). I don't use mate but if it is like gnome: From: https://wiki.gnome.org/Proj

Re: xclip problem

2017-12-22 Thread Paul Gevers
Hi Jude, On 22-12-17 20:04, Jude DaShiell wrote: > I haven't got kde accessible over here yet. Just to avoid confusion, I don't need accessibility support, so I have no clue how much of it doesn't work in KDE. I meant to say, alt-f2 "echo xx > /tmp/yy" produced me a new file called /tmp/yy with t

Re: xclip problem

2017-12-22 Thread Jude DaShiell
I haven't got kde accessible over here yet. No application I've tried to run with it was accessible but that doesn't necessarily mean that will always be the case. I've been doing all of this with mate. On Fri, 22 Dec 2017, Paul Gevers wrote: Date: Fri, 22 Dec 2017 13:56:59 From: Paul Gever

Re: xclip problem

2017-12-22 Thread Paul Gevers
Hi Jude, On 22-12-17 19:26, Jude DaShiell wrote: > as near as I can tell, echo does not work when used after alt-f2 in a > text command. Just tried, for me it works (in KDE). > I also found out it's > necessary to use touch to create a file first before anything can be > sent to that file. That

re: xclip problem

2017-12-22 Thread Jude DaShiell
as near as I can tell, echo does not work when used after alt-f2 in a text command. I'll run set and see if I can direct output to a file in graphical user environment maybe I get lucky. I also found out it's necessary to use touch to create a file first before anything can be sent to that fi

Re: xclip problem

2017-12-22 Thread Jude DaShiell
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

Re: xclip problem

2017-12-22 Thread john doe
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 'd

Re: xclip problem

2017-12-22 Thread Jude DaShiell
No, I used the ">" operator when I ran the command. On Fri, 22 Dec 2017, john doe wrote: Date: Fri, 22 Dec 2017 11:14:47 From: john doe To: debian-accessibility@lists.debian.org Subject: Re: xclip problem Resent-Date: Fri, 22 Dec 2017 16:15:05 + (UTC) Resent-From: debian-accessibility@list

Re: xclip problem

2017-12-22 Thread john doe
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 t

re: xclip problem

2017-12-22 Thread Jude DaShiell
I just checked for dn.txt after running updatedb as root using locate and no results got returned. The file was not produced. --

re: xclip problem

2017-12-22 Thread Jude DaShiell
echo $DISPLAY in graphical user environment provides no output. If I do echo $DISPLAY >dn.txt then check for dn.txt in my $HOME directory later, no such file exists after this operation. I'll check and see if dn.txt is in $HOME/Desktop in fact, I'll check system-wide for it using locate. -

Re: xclip problem

2017-12-22 Thread Samuel Thibault
Jude DaShiell, on jeu. 21 déc. 2017 21:12:45 -0500, wrote: > echo $DISPLAY in speakup returns nothing yet when mate runs, it gets > something for a DISPLAY otherwise I doubt any graphical user environment > could run. You can run echo $DISPLAY in your X environment, and then use e.g. export DISPL