[BRLTTY] bbraille edge keyboard input and cursor tracking with latest development version of brltty

[John Covici]

I always thought you werre supposed to start screen and then start
brltty -- I did not know brltty actually needed to care about screen commands.
On Mon, 29 Jan 2018 01:52:54 -0500,
Cheryl Homiak <cahomiak at gmail.com> wrote:
> 
> Okay I think we have found the problem; I probably should have
> thought of this. I always type /usr/local/bin/screen when I start
> screen. I have screen there because /usr/bin/screen belongs to
> the system and can be updated without me knowing it. So while I
> am using /usr/local/bin/screen, brltty is looking for
> /usr/bin/screen. What is the best way to take care of this?
> Btw it is input and cursor routing that were showing problems; I
> think I inadvertently wrote cursor tracking before.
> 
> 
> -- 
> 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 Mon, 29 Jan 2018, Dave Mielke wrote:
> 
> > [quoted lines by Cheryl Homiak <cahomiak at gmail.com> 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: Dave at Mielke.cc | 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: BRLTTY at brltty.com
> > For general information, go to: 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

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici wb2una
         covici at ccs.covici.com