[quoted lines by Aura Kelloniemi on 2018/03/16 at 17:45 +0200]
>To me hack means a solution which uses a feature in a non-intended way - e.g.
>matches a prompt based on how that prompt is represented in text - instead of
>just knowing what is a prompt and what is not.
But I'd argue that it curr
Dave Mielke writes:
> [quoted lines by Aura Kelloniemi on 2018/03/15 at 08:26 +0200]
> >I'm very sorry if I made an offense. I said, "a bit of a hack", and I
> >consider
> >my own proposal to be such too.
> I don't personally take offense to much, including this issue. To me,
> though,
On Thu, 15 Mar 2018, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2018/03/14 at 23:30 -0400]
>
> >This arrangement lasted for a couple years and went undetected all that time.
>
> I had no problem being totally open about it. It just meant that I had to be
> prepared for the battle (s
[quoted lines by Aura Kelloniemi on 2018/03/15 at 08:26 +0200]
>I'm very sorry if I made an offense. I said, "a bit of a hack", and I consider
>my own proposal to be such too.
I don't personally take offense to much, including this issue. To me, though,
the term "hack" means carelessly thrown t
Dear Dave, and the list!
Dave Mielke writes:
> [quoted lines by Aura Kelloniemi on 2018/03/14 at 10:54 +0200]
> >Another big limitation is that I can't move between two different types of
> >prompts.
> But, in fairness, a regular expression wouldn't support an arbitrary prompt,
> i.e. one
[quoted lines by Nicolas Pitre on 2018/03/14 at 23:30 -0400]
>This arrangement lasted for a couple years and went undetected all that time.
I had no problem being totally open about it. It just meant that I had to be
prepared for the battle (should one arise, as it eventually did).
In the reall
On Wed, 14 Mar 2018, Dave Mielke wrote:
> It's just that network security wasn't understood very well back
> then so the higher management was putting too much trust in the people who
> had
> that job at the time.
My boss at a former job had to put a PC under his desk. That PC would
establish
[quoted lines by Nicolas Pitre on 2018/03/14 at 18:23 -0400]
>>He went quite silent, gave up his attempt to bully me into submission, and
>>tried a different tactic the next day (which he also lost). Perhaps that's
>>a story for another >time, unless you (or anyone else) would like to hear
>>it
On Wed, 14 Mar 2018, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2018/03/14 at 15:49 -0400]
>
> >Good, I agree with that part. But keeping the same analogy: what if one
> >of your kid wants to be a race car driver? You could say to your kid:
> >"you can't because the family car is su
[quoted lines by Nicolas Pitre on 2018/03/14 at 15:49 -0400]
>Good, I agree with that part. But keeping the same analogy: what if one
>of your kid wants to be a race car driver? You could say to your kid:
>"you can't because the family car is suitable for casual driving only"
>or "a race car is
On Wed, 14 Mar 2018, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2018/03/14 at 14:18 -0400]
>
> >My turn to challenge your interpretation. ;-)
>
> Sure. We can have lots of fun with this one. :-)
I'm up to the challenge. ;-)
> >The great responsibility raising your children is inc
[quoted lines by Nicolas Pitre on 2018/03/14 at 14:18 -0400]
>My turn to challenge your interpretation. ;-)
Sure. We can have lots of fun with this one. :-)
>The great responsibility raising your children is incumbent on you. That
>means *your* life becomes more complex, not necessarily theirs
On Wed, 14 Mar 2018, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2018/03/13 at 22:10 -0400]
>
> I accidentally lost a quote that I wanted to challenge. It was something like:
>
> >With great power comes great responsibility (complexity).
>
> I agree with the first part, but not with
[quoted lines by Nicolas Pitre on 2018/03/13 at 22:10 -0400]
I accidentally lost a quote that I wanted to challenge. It was something like:
>With great power comes great responsibility (complexity).
I agree with the first part, but not with the second. In other words, I don't
equate responsibil
On Wed, 14 Mar 2018, Dave Mielke wrote:
> [quoted lines by Nicolas Pitre on 2018/03/13 at 22:10 -0400]
>
> >But the inexperienced wouldn't have to do anything if the default
> >mimics the current behavior, no?
>
> Yes, for sure.
>
> >However such a feature i.e. the ability to modify what NXPRO
[quoted lines by Aura Kelloniemi on 2018/03/14 at 10:54 +0200]
>I consider the current behaviour to be a little bit of a hack itself. I
>consider it to be a big limitation that in order to be able to move from one
>prompt to another I have to first position the braille window on a line which
>alre
[quoted lines by Shérab on 2018/03/14 at 15:21 +0100]
>Would it make sense to have a preference to configure the prompt search
>strategy? Its default could be to the current algorithm (use current
>line as reference for what the prompt is) and then there could be
>another option which would be reg
Hi,
Would it make sense to have a preference to configure the prompt search
strategy? Its default could be to the current algorithm (use current
line as reference for what the prompt is) and then there could be
another option which would be regexp-based?
Shérab.
__
[quoted lines by Nicolas Pitre on 2018/03/13 at 22:10 -0400]
>But the inexperienced wouldn't have to do anything if the default
>mimics the current behavior, no?
Yes, for sure.
>However such a feature i.e. the ability to modify what NXPROMPT matches,
>could be very useful to those who are expe
Hi
Nicolas Pitre writes:
> On Tue, 13 Mar 2018, Dave Mielke wrote:
> > I completely understand your reason and the convenience. I'm just not
> > convinced
> > that it'd actually work all that well as a general facility for the
> > inexperienced.
> But the inexperienced wouldn't have to
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
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
[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
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 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
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
26 matches
Mail list logo
