Term::Cap -- Setting terminal type under Windows XP

[Chubasco]

I am trying to get Term::Cap to run under Windows XP. When running the code
snippet below from the Term::Cap documentation, I get the message "TERM not
set at termcapxx.pl line 2". What is the procedure for setting the TERM
terminal type on Windows XP?


require Term::Cap;
$terminal = Tgetent Term::Cap { TERM => undef, OSPEED => $ospeed };
$terminal->Trequire(qw/ce ku kd/);
$terminal->Tgoto('cm', $col, $row, $FH);
$terminal->Tputs('dl', $count, $FH);
$terminal->Tpad($string, $count, $FH);

[Chubasco]

I am submitting this message again. Doesn't anyone out there know about
using termcap under Windows XP?

I am trying to get Term::Cap to run under Windows XP. When running the code
snippet below from the Term::Cap documentation, I get the message "TERM not
set at termcapxx.pl line 2". What is the procedure for setting the TERM
terminal type on Windows XP?


require Term::Cap;
$terminal = Tgetent Term::Cap { TERM => undef, OSPEED => $ospeed };
$terminal->Trequire(qw/ce ku kd/);
$terminal->Tgoto('cm', $col, $row, $FH);
$terminal->Tputs('dl', $count, $FH);
$terminal->Tpad($string, $count, $FH);

[Sisyphus]

"Chubasco" <eastonbeymer@cox.net> wrote in message
news:P7Neg.3677$_m5.1414@fed1read09...

> I am submitting this message again. Doesn't anyone out there know about
> using termcap under Windows XP?
>

It seems that the Cygwin developers know something about this as Term::Cap
works fine in Cygwin's shell on Windows 2000 (and presumably XP as well). By
"works fine" I mean that all tests in the Term::Cap-1.09 test suite pass
under Cygwin (whereas on native windows they are all simply skipped).

The Term::Cap-1.09 documentation says that the module will "use capabilities
from a terminal capability (termcap) database" - and I guess that the
"terminal capability database" is missing in the native windows environment.
The problem may go well beyond that - faik it may be that Term::Cap *cannot*
be applied to the cmd.exe shell.

Does Win32::Console (which is part of the libwin distro) provide you with
what you need ? (I know so little about these matters that I cannot even
confirm that's a sensible question :-)

Hope there's something there that helps.

Cheers,
Rob

[Ilya Zakharevich]

[A complimentary Cc of this posting was sent to
Sisyphus
<sisyphus1@nomail.afraid.org>], who wrote in article <447eac65$0$22807$afc38c87@news.optusnet.com.au> :

>
> "Chubasco" <eastonbeymer@cox.net> wrote in message
> news:P7Neg.3677$_m5.1414@fed1read09...

> > I am submitting this message again. Doesn't anyone out there know about
> > using termcap under Windows XP?
> >

>
> It seems that the Cygwin developers know something about this as Term::Cap
> works fine in Cygwin's shell on Windows 2000 (and presumably XP as well). By
> "works fine" I mean that all tests in the Term::Cap-1.09 test suite pass
> under Cygwin (whereas on native windows they are all simply skipped).
>
> The Term::Cap-1.09 documentation says that the module will "use capabilities
> from a terminal capability (termcap) database" - and I guess that the
> "terminal capability database" is missing in the native windows environment.
> The problem may go well beyond that - faik it may be that Term::Cap *cannot*
> be applied to the cmd.exe shell.

I would be very surprised if TERM=ansi with "standard" termcap file
won't work. Put it somewhere, and set TERMCAP appropriately to check.

If this works, this implies that on Win32 etc, Term::Cap should
fallback to this value if it can't find the database or TERM.

Hope this helps,
Ilya