From jason at jasonjgw.net Sun Dec 1 11:03:51 2019 From: jason at jasonjgw.net (Jason White) Date: Sun, 01 Dec 2019 11:03:51 -0500 Subject: slightly, improving how the Links browser speaks? In-Reply-To: References: Message-ID: I don't know how Links is laid out on screen, but assuming that it has a fixed-size window for the Web page content, you could set up a window in your DOS screen reader that covers that area, then read that window whenever you need to - for example, when you move to a new screen of text. This isn't ideal, of course, but it would be better than reviewing line by line. I remember having Doslynx, but I'm not sure whether I ever had Links (the chain) on my DOS system. I did have DOS versions of a lot of Unix-based programs. ?On 11/29/19, 10:51, "Speakup on behalf of Karen Lewellen" wrote: Hi folks, Hope to ask this clearly, as it may also apply to speakup, at least for those using a command line setup. My goal mirrors the command line options included in some tools that write information to the screen in a way that speech happens largely automatically. For example, some programs call this writing to the BIOS, or used to do as much. My ssh telnet client for example has a -b option that performs the function I desire. I am seeking such a command line option for the links as in the chain browser. I believe? it should exist because there is a command line option that establishes numbered links. hoping that my question is clear, can anyone tell me what command line option improves how content is spoken when using the links browser? Thanks, Karen _______________________________________________ Speakup mailing list Speakup at linux-speakup.org http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup From klewellen at shellworld.net Sun Dec 1 12:37:59 2019 From: klewellen at shellworld.net (Karen Lewellen) Date: Sun, 1 Dec 2019 12:37:59 -0500 (EST) Subject: slightly, improving how the Links browser speaks? In-Reply-To: References:

Message-ID: Well given this dos compile of Links the chain with JavaScript was released on 20 August 2019, I imagine you did not have it previously. Further, my dos screen reader already provides such windows. To be sure the window method is not speech while things are progressing, which is my goal, but it is something smiles. Thanks, Karen On Sun, 1 Dec 2019, Jason White wrote: > I don't know how Links is laid out on screen, but assuming that it has a fixed-size window for the Web page content, you could set up a window in your DOS screen reader that covers that area, then read that window whenever you need to - for example, when you move to a new screen of text. > > This isn't ideal, of course, but it would be better than reviewing line by line. > > I remember having Doslynx, but I'm not sure whether I ever had Links (the chain) on my DOS system. I did have DOS versions of a lot of Unix-based programs. > > ?On 11/29/19, 10:51, "Speakup on behalf of Karen Lewellen" wrote: > > Hi folks, > Hope to ask this clearly, as it may also apply to speakup, at least for > those using a command line setup. > My goal mirrors the command line options included in some tools that write > information to the screen in a way that speech happens largely > automatically. > For example, some programs call this writing to the BIOS, or used to do as > much. > My ssh telnet client for example has a -b option that performs the > function I desire. > I am seeking such a command line option for the links as in the chain > browser. I believe? it should exist because there is a command line > option that establishes numbered links. > hoping that my question is clear, can anyone tell me what command line > option improves how content is spoken when using the links browser? > Thanks, > Karen > > > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > > > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > From astrope at tabbweb.com Sun Dec 15 20:20:51 2019 From: astrope at tabbweb.com (Trevor Astrope) Date: Sun, 15 Dec 2019 20:20:51 -0500 (EST) Subject: google doesn't like us In-Reply-To: <20191115192337.GA31439@my-p4> References: <20191115192337.GA31439@my-p4> Message-ID: bing.com works too. Was using it while google was sucking. On Fri, 15 Nov 2019, David wrote: > My wife Darlene says lose google and switch to duckduckgo.com > No clutter and still a decent search. > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > From jdashiel at panix.com Thu Dec 19 10:45:24 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 19 Dec 2019 10:45:24 -0500 Subject: audionoir.sh Message-ID: Here's a script that plays audionoir.sh now. Modify the station variable though to another working radio stream and you can get it playing that stream too. #!/usr/bin/env bash # file: audionoir.sh - listen to audionoir radio script # from: radio.sh - template for new stations station="http://198.245.61.123:8000/noir/" rvlc --quiet --novideo --key-vol-up 123 --no-skinned-playlist $station -- From didier at slint.fr Thu Dec 19 11:19:50 2019 From: didier at slint.fr (Didier Spaier) Date: Thu, 19 Dec 2019 17:19:50 +0100 Subject: audionoir.sh In-Reply-To: References: Message-ID: Hi Jude, Maybe you intended to post in another list, like the Slint mailing list? I ask, as this works but does not seem to be involve speakup. Best, Didier Le 19/12/19 ? 16:45, Jude DaShiell a ?crit?: > Here's a script that plays audionoir.sh now. Modify the station variable > though to another working radio stream and you can get it playing that > stream too. > > #!/usr/bin/env bash > # file: audionoir.sh - listen to audionoir radio script > # from: radio.sh - template for new stations > station="http://198.245.61.123:8000/noir/" > rvlc --quiet --novideo --key-vol-up 123 --no-skinned-playlist $station > From jdashiel at panix.com Thu Dec 19 11:32:25 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Thu, 19 Dec 2019 11:32:25 -0500 Subject: audionoir.sh In-Reply-To: References:

Message-ID: In the past other projects not related to speakup had been made available some of which on the speakup web page itself so that was my reason for posting this script here. On Thu, 19 Dec 2019, Didier Spaier wrote: > Date: Thu, 19 Dec 2019 11:19:50 > From: Didier Spaier > Reply-To: Speakup is a screen review system for Linux. > > To: speakup at linux-speakup.org > Subject: Re: audionoir.sh > > Hi Jude, > > Maybe you intended to post in another list, like the Slint mailing list? > > I ask, as this works but does not seem to be involve speakup. > > Best, > > Didier > > Le 19/12/19 ? 16:45, Jude DaShiell a ?crit?: > > Here's a script that plays audionoir.sh now. Modify the station variable > > though to another working radio stream and you can get it playing that > > stream too. > > > > #!/usr/bin/env bash > > # file: audionoir.sh - listen to audionoir radio script > > # from: radio.sh - template for new stations > > station="http://198.245.61.123:8000/noir/" > > rvlc --quiet --novideo --key-vol-up 123 --no-skinned-playlist $station > > > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > -- From greg at gregn.net Thu Dec 19 19:12:18 2019 From: greg at gregn.net (Gregory Nowak) Date: Thu, 19 Dec 2019 17:12:18 -0700 Subject: audionoir.sh In-Reply-To: References:

Message-ID: <20191220001218.GA5531@gregn.net> Here's a refresher from the list archives: Greg On Thu, Dec 19, 2019 at 11:32:25AM -0500, Jude DaShiell wrote: > In the past other projects not related to speakup had been made > available some of which on the speakup web page itself so that was my > reason for posting this script here. -- web site: http://www.gregn.net gpg public key: http://www.gregn.net/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) If we haven't been in touch before, e-mail me before adding me to your contacts. -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org From didier at slint.fr Fri Dec 20 01:32:30 2019 From: didier at slint.fr (Didier Spaier) Date: Fri, 20 Dec 2019 07:32:30 +0100 Subject: audionoir.sh In-Reply-To: <20191220001218.GA5531@gregn.net> References:

<20191220001218.GA5531@gregn.net> Message-ID: <1445baa1-7312-e4b9-ad4d-ba32117d2ee0@slint.fr> Well, I certainly don't want to be perceived by Kirk or anyone else as a list Nazi, sorry if my answer leaded to such a conclusion. I should have instead just suggested that Jude posted his tip *also* in other lists, my mistake. Best regards, Didier Le 20/12/19 ? 01:12, Gregory Nowak a ?crit?: > Here's a refresher from the list archives: > > > > Greg > > > On Thu, Dec 19, 2019 at 11:32:25AM -0500, Jude DaShiell wrote: >> In the past other projects not related to speakup had been made >> available some of which on the speakup web page itself so that was my >> reason for posting this script here. From kirk at reisers.ca Sun Dec 22 21:46:18 2019 From: kirk at reisers.ca (Kirk Reiser) Date: Sun, 22 Dec 2019 21:46:18 -0500 (EST) Subject: speakup locking box on latest linux 5.3.15-1 Message-ID: Hello folks: It appears the bug that visited speakup back in late August is back and active. In kernel version 5.3.15-1 built on 2019-12-07. It can very easily be reproduced by hitting the next-word or previous-word functions quickly in series. In fact it is veryd ifficult to not trigger the bug. This is in debian sid BTW. My machines are amd64 based so I'm not sure if it's active on Intel processors. Kirk From janina at rednote.net Tue Dec 31 06:41:29 2019 From: janina at rednote.net (Janina Sajka) Date: Tue, 31 Dec 2019 06:41:29 -0500 Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: References: Message-ID: <20191231114129.GA1937@rednote.net> Kirk: I think I'm also seeing this on my Arch system. The behavior is speech dies, and there seems no way to get it back short of a reboot. Best, Janina Kirk Reiser writes: > Hello folks: It appears the bug that visited speakup back in late > August is back and active. In kernel version 5.3.15-1 built on > 2019-12-07. It can very easily be reproduced by hitting the next-word > or previous-word functions quickly in series. In fact it is veryd > ifficult to not trigger the bug. This is in debian sid BTW. My > machines are amd64 based so I'm not sure if it's active on Intel > processors. > > Kirk > > > > > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa From kirk at reisers.ca Tue Dec 31 09:46:29 2019 From: kirk at reisers.ca (Kirk Reiser) Date: Tue, 31 Dec 2019 09:46:29 -0500 (EST) Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: <20191231114129.GA1937@rednote.net> References: <20191231114129.GA1937@rednote.net> Message-ID: Yes Janina: On my boxes the machine is locked up solid as in not able to even ssh or ping the machine. I have had to revert back to a 5.2.x series kernel to by-pass the problem. I tried three different 5.3.x kernels extensively before reverting. Kirk On Tue, 31 Dec 2019, Janina Sajka wrote: > Kirk: > > I think I'm also seeing this on my Arch system. > > The behavior is speech dies, and there seems no way to get it back short > of a reboot. > > Best, > > Janina > > Kirk Reiser writes: >> Hello folks: It appears the bug that visited speakup back in late >> August is back and active. In kernel version 5.3.15-1 built on >> 2019-12-07. It can very easily be reproduced by hitting the next-word >> or previous-word functions quickly in series. In fact it is veryd >> ifficult to not trigger the bug. This is in debian sid BTW. My >> machines are amd64 based so I'm not sure if it's active on Intel >> processors. >> >> Kirk >> >> >> >> >> _______________________________________________ >> Speakup mailing list >> Speakup at linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > From didier at slint.fr Tue Dec 31 10:30:06 2019 From: didier at slint.fr (Didier Spaier) Date: Tue, 31 Dec 2019 16:30:06 +0100 Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: References: <20191231114129.GA1937@rednote.net> Message-ID: <8d32a2c2-8cbf-c5c7-6f48-b4fd440a5da8@slint.fr> Hi Kirk and Janina, I won't ship a 5.3.x Kernel in Slint anyway as it is officially EOL upstream, however I plan to provide a 5.4 kernel soon and would like to have it tested wrt this issue. I do not own a hard synth so can only test with speakup_soft myself, but I could ask Slint users to do so with a hard synth (ltlk at least and probably apollo as well). With which driver did you try: soft or hard and then which hard synth? Also Janina, does this issue occur also with linux 5.4.6.arch3-1? As an aside, Kirk did you try one of the package labeled linux-image-5.4.0-1- provided for Debian SID? Best regards, Didier Le 31/12/19 ? 15:46, Kirk Reiser a ?crit?: > Yes Janina: On my boxes the machine is locked up solid as in not able > to even ssh or ping the machine. > > I have had to revert back to a 5.2.x series kernel to by-pass the > problem. I tried three different 5.3.x kernels extensively before > reverting. > > ? Kirk > > On Tue, 31 Dec 2019, Janina Sajka wrote: > >> Kirk: >> >> I think I'm also seeing this on my Arch system. >> >> The behavior is speech dies, and there seems no way to get it back short >> of a reboot. >> >> Best, >> >> Janina >> >> Kirk Reiser writes: >>> Hello folks: It appears the bug that visited speakup back in late >>> August is back and active. In kernel version 5.3.15-1 built on >>> 2019-12-07. It can very easily be reproduced by hitting the next-word >>> or previous-word functions quickly in series. In fact it is veryd >>> ifficult to not trigger the bug. This is in debian sid BTW. My >>> machines are amd64 based so I'm not sure if it's active on Intel >>> processors. >>> >>> ? Kirk From kirk at reisers.ca Tue Dec 31 10:53:24 2019 From: kirk at reisers.ca (Kirk Reiser) Date: Tue, 31 Dec 2019 10:53:24 -0500 (EST) Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: <8d32a2c2-8cbf-c5c7-6f48-b4fd440a5da8@slint.fr> References: <20191231114129.GA1937@rednote.net> <8d32a2c2-8cbf-c5c7-6f48-b4fd440a5da8@slint.fr> Message-ID: Hey Didier: All of the kernels I tested were debian sid packages. The most recent was a December twelve build I believe. I have not seen any 5.4.x kernels available under sid yet. Admittedly, I don't try to upgrade every day or anything. I pretty much strictly use speakup_soft with espeakup. I first thought it might be an espeakup problem since it is as flakey as ever with the lack of speech interrupt ability in a timely manner but the problem still persists with my old solid espeakup and the old espeak libraries. I would be willing to test your kernels if you could send me a drop in replacement with the System.map etc. Kirk On Tue, 31 Dec 2019, Didier Spaier wrote: > Hi Kirk and Janina, > > I won't ship a 5.3.x Kernel in Slint anyway as it is officially EOL > upstream, however I plan to provide a 5.4 kernel soon and would like > to have it tested wrt this issue. > > I do not own a hard synth so can only test with speakup_soft myself, but > I could ask Slint users to do so with a hard synth (ltlk at least and > probably apollo as well). > > With which driver did you try: soft or hard and then which hard synth? > > Also Janina, does this issue occur also with linux 5.4.6.arch3-1? > > As an aside, Kirk did you try one of the package labeled > linux-image-5.4.0-1- provided for Debian SID? > > Best regards, > > Didier > > Le 31/12/19 ? 15:46, Kirk Reiser a ?crit?: >> Yes Janina: On my boxes the machine is locked up solid as in not able >> to even ssh or ping the machine. >> >> I have had to revert back to a 5.2.x series kernel to by-pass the >> problem. I tried three different 5.3.x kernels extensively before >> reverting. >> >> ? Kirk >> >> On Tue, 31 Dec 2019, Janina Sajka wrote: >> >>> Kirk: >>> >>> I think I'm also seeing this on my Arch system. >>> >>> The behavior is speech dies, and there seems no way to get it back short >>> of a reboot. >>> >>> Best, >>> >>> Janina >>> >>> Kirk Reiser writes: >>>> Hello folks: It appears the bug that visited speakup back in late >>>> August is back and active. In kernel version 5.3.15-1 built on >>>> 2019-12-07. It can very easily be reproduced by hitting the next-word >>>> or previous-word functions quickly in series. In fact it is veryd >>>> ifficult to not trigger the bug. This is in debian sid BTW. My >>>> machines are amd64 based so I'm not sure if it's active on Intel >>>> processors. >>>> >>>> ? Kirk > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup From samuel.thibault at ens-lyon.org Tue Dec 31 11:03:33 2019 From: samuel.thibault at ens-lyon.org (Samuel Thibault) Date: Tue, 31 Dec 2019 17:03:33 +0100 Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: References: <20191231114129.GA1937@rednote.net> <8d32a2c2-8cbf-c5c7-6f48-b4fd440a5da8@slint.fr> Message-ID: <20191231160333.llw4xqg55jyudkzg@function> Hello, Kirk Reiser, le mar. 31 d?c. 2019 10:53:24 -0500, a ecrit: > Hey Didier: All of the kernels I tested were debian sid packages. The > most recent was a December twelve build I believe. I have not seen any > 5.4.x kernels available under sid yet. Admittedly, I don't try to > upgrade every day or anything. It has been uploaded to sid only recently, on 28th december :) Samuel From kirk at reisers.ca Tue Dec 31 11:13:47 2019 From: kirk at reisers.ca (Kirk Reiser) Date: Tue, 31 Dec 2019 11:13:47 -0500 (EST) Subject: speakup locking box on latest linux 5.3.15-1 In-Reply-To: <20191231160333.llw4xqg55jyudkzg@function> References: <20191231114129.GA1937@rednote.net> <8d32a2c2-8cbf-c5c7-6f48-b4fd440a5da8@slint.fr> <20191231160333.llw4xqg55jyudkzg@function> Message-ID: Hi Samuel: Very cool. I will do an upgrade today and see how that works out. Thank you. Kirk On Tue, 31 Dec 2019, Samuel Thibault wrote: > Hello, > > Kirk Reiser, le mar. 31 d?c. 2019 10:53:24 -0500, a ecrit: >> Hey Didier: All of the kernels I tested were debian sid packages. The >> most recent was a December twelve build I believe. I have not seen any >> 5.4.x kernels available under sid yet. Admittedly, I don't try to >> upgrade every day or anything. > > It has been uploaded to sid only recently, on 28th december :) > > Samuel > _______________________________________________ > Speakup mailing list > Speakup at linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup