[BRLTTY] how to use brltty on mac

Tue Sep 5 15:44:39 EDT 2017

Hi!
Ok, so screen is a kind of screenReader then?
/A

> 4 sep. 2017 kl. 20:29 skrev Cheryl Homiak <cah4110 at icloud.com>:
> 
> Screen has to be used on the Mac because it only works in Terminal and we have no ability to access the Mac screen. We wouldn't be able to use brltty on the Mac at all if we did not use screen.
> 
> Hth.
> 
> -- 
> Cheryl
> 
> May the words of my mouth
> and the meditation of my heart
> be acceptable to You, Lord,
> my rock and my Redeemer.
> (Psalm 19:14 HCSB)
> 
> 
> 
> 
> On Sep 4, 2017, at 11:53 AM, Anders Holmberg <anders at pipkrokodil.se <mailto:anders at pipkrokodil.se>> wrote:
> 
> Hi!
> The screen thing makes me more confused so i wonder if this really is needed?
> I never use screen on ubuntu in console mode either.
> /A
> 
>> 1 sep. 2017 kl. 20:00 skrev Cheryl Homiak <cah4110 at icloud.com <mailto:cah4110 at icloud.com>>:
>> 
>> If you are going to post a readme to the list I can take a look and add my two-cents' worth too. It actually can be done without Macports or Homebrew but it is definitely easier with one of those. There is actually a version of git included with the Mac system but git also usually gets installed even without having to specifically request it with Macports. If you do install git, you do it using sudo the same as you do for Macports. This isn't quite the same as actually becoming root to do it but you do have to have an administrative user account rather than a standard one; most Mac users would have an admin account.
>>  Usually .cfg-darwin works best but there have been times when this failed and the ./configure worked instead; if one fails I try the other though I try the darwin one first. People need to be aware that brltty works only in terminal on the Mac. The screen issue isn't really a big problem; I install the screen program for use with brltty in /usr/local/bin. I am not sure what the words "joined" and "soft" mean here; probably it is obvious and my brain just isn't getting it.
>> 
>> 
>> 
>> On Sep 1, 2017, at 10:41 AM, rmgls <rmgls at orange.fr <mailto:rmgls at orange.fr>> wrote:
>> 
>> Hi Dave,
>> 
>> I will write something
>> $
>> 
>> Once done  and tested  I will send it to the list.
>> 
>> For now:  
>> Joined is my  working screen to install somewhere
>> And to explicitly  start with the complete path
>> Because if you type only (screen
>>  Mac starts /usr/bin/screen which of course is not patched and does not work.
>> In the readme.mac I will explain how to solve this problem.
>> 
>> 2.  One must install macport (www.macports.org/ <http://www.macports.org/> )  => downloads
>> =>  macport version for your system:  (Sierra and so on).
>> Install it.
>> 
>> With voiceover open the terminal (in utilities: cmd+shift+u).
>> 
>> Running the terminal:
>> You must install git from the macport soft:
>> Port install git as root. I suppose you have all rights on your machine.
>> 
>> And after  as usual: git clone … you know that.
>> Autogen. And if all goes well (you have all dependencies!) (port search SOMESOFT will tell if it is found).
>> After that, run cfg-darwin ( and make and as root make install.
>> 
>> NOTE: you must download first of all Xcode on the App Store.
>> And after you must accept the licenser,
>> And download the command line tools.
>> 
>> Hope I don’t forget something.
>>  I will see to write a complete readme.mac.
>>  Waiting it, if you have problems feel free to ask.
>> 
>> Regards
>> 
>> Raoul MEGELAS
>> rmgls at orange.fr <mailto:rmgls at orange.fr>
>> 
>> 
>>> On Sep 1, 2017, at 4:35 PM, Dave Mielke <dave at mielke.cc <mailto:dave at mielke.cc>> wrote:
>>> 
>>> [quoted lines by rmgls on 2017/09/01 at 15:38 +0200]
>>> 
>>>> Email me privately I will  help you.
>>> 
>>> We really need a README.Mac that includes all known information on this topic. 
>>> Is it possible that you and/or Cheryl could write one? I can't, since I don't 
>>> even have a Mac on which to verify anything, but I don't mind editing whatever 
>>> either of you sends me so that you don't need to be concerned with creating a 
>>> perfect document.
>>> 
>>> -- 
>>> Dave Mielke           | 2213 Fox Crescent | http://Mielke.cc/ <http://mielke.cc/>
>>> Phone: 1-613-726-0014 | Ottawa, Ontario   | http://Mielke.cc/bible/ <http://mielke.cc/bible/>
>>> EMail: Dave at Mielke.cc <mailto:Dave at Mielke.cc> | Canada  K2A 1H7   | The Bible is the very Word of God.
>>> _______________________________________________
>>> This message was sent via the BRLTTY mailing list.
>>> To post a message, send an e-mail to: BRLTTY at brltty.com <mailto:BRLTTY at brltty.com>
>>> For general information, go to: http://brltty.com/mailman/listinfo/brltty <http://brltty.com/mailman/listinfo/brltty>
>> 
>> _______________________________________________
>> This message was sent via the BRLTTY mailing list.
>> To post a message, send an e-mail to: BRLTTY at brltty.com <mailto:BRLTTY at brltty.com>
>> For general information, go to: http://brltty.com/mailman/listinfo/brltty <http://brltty.com/mailman/listinfo/brltty>
>> _______________________________________________
>> This message was sent via the BRLTTY mailing list.
>> To post a message, send an e-mail to: BRLTTY at brltty.com <mailto:BRLTTY at brltty.com>
>> For general information, go to: http://brltty.com/mailman/listinfo/brltty <http://brltty.com/mailman/listinfo/brltty>
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.com <mailto:BRLTTY at brltty.com>
> For general information, go to: http://brltty.com/mailman/listinfo/brltty <http://brltty.com/mailman/listinfo/brltty>
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at brltty.com
> For general information, go to: http://brltty.com/mailman/listinfo/brltty

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.com/pipermail/brltty/attachments/20170905/6b99f76e/attachment.html>