On So. 01. Mär. 2009, 17:41:05, user42@zip.com.au wrote:
Show quoted text> "Karl Gaissmaier via RT" <bug-PerlIO-via-EscStatus@rt.cpan.org> writes:
> >
> > thanks a lot for your Regexp::Common::ANSIescape. I use it for network
> > device automation.
>
> Glad you like it. (Incidentally, it's only bundled with my EscStatus
> stuff because I wasn't sure it'd have a wider audience :-)
It has, sure. A lot of people need regexes for ANSI escape sequences.
Show quoted text>
> > Question: Could you please add the often used (in VT100 compatible
> > terminals)
> > CSI ? ... (DEC Private Mode Set (DECSET))
>
> Yep, I think that's feasible. In fact my reading of the ANSI/ECMA would
> be that all I should do is allow < = > ? characters in the parameter
> part ... whereas now I've just got "[0-9;]" (in the pattern() func).
>
> Spec 5.4.1(b) says when it starts with a ? the parameters are private
> and unspecified, but I'm guessing they're still only chars 0x30 to 0x3F.
> Does that sound right to you?
Uups, I'm really no ANSI or VT expert, I'm a network fuzzy and
perl programmer.
Show quoted text>
> I see there's other DEC vt escapes which are not CSI style. Are you
> suffering under some of them too?
No, I'm not suffering of them, but the question is how you mark
them in your Regexp::Common namespace right.
If you find a well known subset you can spend a proper name, but
if you only support an unspecified subset, how will you name
this?
Show quoted text> ... I'm not sure I want to visit the
> obscure features of every terminal type in the world! :-)
Yep, that's clear ;-)
Best Regards and many thanks for your time and effort
Charly
