[quoted lines by Cheryl Homiak <[email protected]> on 2018/01/28 at 22:54 -0600]
>Maybe I am not understanding, but I don't think there's time to check >the path between the time I type the command to start brltty and it >actually starts. Is that what you meant? No. I mean to check $PATH just before you start brltty. At that same point, you might also verify that screen is in $PATH another way: type screen The type command should display the path to the screen command that's being found. That might be worth verifying in case you have more than one screen and the wrong one is being invoked. >I can tell you that /usr/local/bin is in the path normally. Here's another thing to try, and this can be done after brltty has been started. Nevertheless, please do it from the same session. Right after starting brltty would be best. Execute this command: screen -p 1 -X stuff a That should input the letter a, which, in turn, should be echoed. Does that work or do you get an error message? >Meanwhile here is the log with the added item. It shows that the screen driver is doing exactly the right thing, but still no error message from screen showing why it's failing. -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: 1-613-726-0014 | Canada K2A 1H7 | _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.com/mailman/listinfo/brltty
