Hi
I'm missing a feature which would allow me to define a regular expression
pattern that would be matched to decide what content on screen is a prompt and
what is not for NXPROMPT/PRPROMPT commands. This would most likely be
defined in brltty.conf.
Currently I think that when using the above men
[quoted lines by Aura Kelloniemi on 2018/03/13 at 13:49 +0200]
>I'm missing a feature which would allow me to define a regular expression
>pattern that would be matched to decide what content on screen is a prompt and
>what is not for NXPROMPT/PRPROMPT commands. This would most likely be
>defined
Hello,
Dave Mielke writes:
> [quoted lines by Aura Kelloniemi on 2018/03/13 at 13:49 +0200]
> >I'm missing a feature which would allow me to define a regular expression
> >pattern that would be matched to decide what content on screen is a prompt
> >and
> >what is not for NXPROMPT/PRPROMPT
[quoted lines by Aura Kelloniemi on 2018/03/13 at 14:59 +0200]
> > That wouldn't match current behaviour at all. In fact, it'd match any line
> > at
> > all whose first space isn't in column 1. Current behaviour considers the
> > content of the current line in order to know exactly what to matc
Aura Kelloniemi writes:
> What I would want to have is a Perl-style (or sed-style) regex substitution,
> where the original string is the current line. Like this:
> s/^([^ ]+ ).*/\1/
> Then the result of the substitution is compared to screen contents to find
> other prompts.
No, even that
On Tue, 13 Mar 2018, Dave Mielke wrote:
> [quoted lines by Aura Kelloniemi on 2018/03/13 at 14:59 +0200]
>
> > > Maybe your shell prompt looks like that, but, since a shell's prompt is
> > > configurable, I'm sure it's far from a common case. Would we really want
> > > every
> > > single brltt
