Ports 搜索

Perl 5 ships with a module called Term::ReadLine which is an interface to command line editing and recall. The version that ships with Perl is only a stub, and offers little functionality. This module supplements Term::ReadLine so that it uses GNU readline, which comes with FreeBSD. Applications that use Term::ReadLine do not need to be modified to gain the benefits of this package; it will happen transparently upon installation.

This module helps run test scripts in IDEs like Komodo.

Term::Sk is a class to implement a progress indicator ("Sk" is a short form for "Show Key"). This is used to provide immediate feedback for long running processes.

This is another framework for writing test scripts. It is loosely inspired by Test::More, and has most of its functionality, but it is not a drop-in replacement.

This is a quick implementation of the minimal interface to Readline libraries.

ReadLine::TTYtter is a fork of the Term::ReadLine::Perl module, allowing to edit a command line. This module have UTF-8 support, let erase or repaint the prompt and to hook a process to further line control.

This package provides a set of modules that form an interactive input buffer written in plain perl with minimal dependencies. It features almost all key-bindings described in the posix spec for the sh(1) utility with some extensions like multi-line editing; this includes a vi-command mode with a save-buffer (for copy-pasting) and an undo-stack.

Test::LeakTrace provides several functions that trace memory leaks. This module scans arenas, the memory allocation system, so it can detect any leaked SVs in given blocks. Leaked SVs are SVs which are not released after the end of the scope they have been created. These SVs include global variables and internal caches. For example, if you call a method in a tracing block, perl might prepare a cache for the method. Thus, to trace true leaks, no_leaks_ok() and leaks_cmp_ok() executes a block more than once.

Term::Screen is a very simple screen positioning module that should work wherever `Term::Cap' does. It is set up for Unix using stty's but these dependencies are isolated by evals in the `new' constructor. Thus you may create a child module implementing Screen with MS-DOS, ioctl, or other means to get raw and unblocked input. This is not a replacement for Curses -- it has no memory. This was written so that it could be easily changed to fit nasty systems, and to be available first thing.

Term::ScreenColor adds ANSI coloring support, along with a few other useful methods, to those provided in Term::Screen.