Free strike anywhere matches software for linux

streamripagent is a simple Amarok script that watches the tracks streamed in Amarok. If any of the regexps in ~/.streamripagent matches the current title, streamripper is started and the track is ripped to a specified directory.

Its not exactly an amarok script that you can manage with the amarok script manager, but its related to amarok, so I put it in this category.

Please read the README before installing and running streamripagent!

Simple PHP Internet Traffic Shaping in short SPITS, is a PHP Web Interface for managing traffic control queueing disciplines (qdiscs) and classes. Iptables rules are used in order to classify the packets. It currently only supports few qdiscs and iptables rules with few matches.

File::Searcher is a searches for files and performs search/replacements on matching files.

SYNOPSIS

use File::Searcher;
my $search = File::Searcher->new(*.cgi);
$search->add_expression(name=>street,
search=>1234 Easy St.,
replace=>456 Hard Way,
options=>i);
$search->add_expression(name=>department,
search=>(Dept.|Department)(s+)(d+),
replace=>$1$2$3,
options=>im);
$search->add_expression(name=>place,
search=>Portland, OR(.*?)97212,
replace=>Vicksburg, MI${1}49097,
options=>is);
$search->start;
# $search->interactive; SEE File::Searcher::Interactive
@files_matched = $search->files_matched;
print "Files Matchedn";
print "t" . join("nt", @files_matched) . "n";
print "Total Files:t" . $search->file_cnt . "n";
print "Directories:t" . $search->dir_cnt . "n";
my @files_replaced = $search->expression(street)->files_replaced;
my @files_replaced = $search->expression($expression)->files_replaced;
my %matches = $search->expression(street)->matches;
my %replacements = $search->expression(street)->replacements;

File::Searcher allows for the traversing of a directory tree for files matching a Perl regular expression. When a match is found, the statistics are stored and if the file is a text file a series of searches and replacements can be performed. File::Searcher has options that allow for backing-up / archiving files and has OO access to reporting and statistics of matches and replacements.

Parse::RandGen::Regexp is a Perl module for regular expression Condition element.

Regexp is a Condition element that matches the given compiled regular expression. For picking random data, the regular expression is parsed into its component Subrules, Literals, CharClasses, etc.... Therefore, the pick functionality for a regular expression is ultimately the same as the pick functionality of a Rule (including the limitations w/r to greediness - see Rule).

Regexp is also useful as a standalone class. It supports captures (named and indexed), which can be referenced in a call to the pick() function to force the captures to match the specified data, while leaving the rest of the data to be generated randomly.

METHODS

new

Creates a new Regexp. The first argument (required) is the regular expression element (e.g. qr/foo(bar|baz)+d{1,10}/). All other arguments are named pairs.

element

Returns the Regexp element (i.e. the compiled regular expression itself).

numCaptures

Returns the number of captures (e.g. $1, $2, ...$n) in the regular expression.

nameCapture

Give names to capture numbers for the regular expression. The arguments to this function are capture# => "name" pairs (e.g. nameCapture(1=>"directory", 2=>"file", 3=>"extension")).

capture

Returns the Rule object that represents the specified capture. The capture can be specified by number or by name (the name is set by the nameCapture() function).

pick

Randomly generate data (text) that matches (or does not) this regular expression.
Takes a "match" boolean argument that specifies whether to match the regular expression or deliberately not match it.

Also takes a "captures" hash argument that has pairs of capture numbers (or names) and their desired value. This allows the generated data to have user-specified constraints while allowing the rest of the regular expression to choose random data. If "match" is false, the user-specified "captures" values are still used (which may cause the data to match even though it was not supposed to).

Example:
$re->pick(match=>1,
captures=>{ 1=>"http", 2=>"www", 3=>"yahoo", 4=>"com" });

Movie Mapper project is a small program for indexing movie collections.

Movie Mapper is a small program for indexing movie collections. It browses given directory trees, searching for text files that contain IMDB URLs.

These URLs are used to generate database entries for movies.

Movie Mapper can also be used for offline indexing by creating text files that contain offline movie titles.

It tries to find matches from IMDB for those titles listed in the text files.

Net::ACL::Match::IP is a class matching IP addresses against an IP or network.

SYNOPSIS

use Net::ACL::Match::IP;
# Constructor
$match = new Net::ACL::Match::IP(1,10.0.0.0/8);
# Accessor Methods
$netmaskobj = $match->net($netmaskobj);
$netmaskobj = $match->net($net);
$index = $match->index($index);
$rc = $match->match($ip);
__top

This module is just a wrapper of the Net::Netmask module to allow it to operate automatically with Net::ACL::Rule.

XSearch project bridges the gap between Beagle (simple interface, large search net) and find/grep (powerful searching, small search net).

What is XSearch?

A fast real-time search engine for displaying all regular expression matches within a file, across multiple directories.

Why XSearch?

Linux currently has two leading search methods:

1.Beagle – simple to use, but shows too many matches.
2.Find/Grep – hard to use, but provides exact matching.

XSearch tales the best features from both.

It provides a simple to use interface, but has the power of find and grep combined. In addition, the end search result is an easy to browse list of matching files, and matching lines.

Who would benefit from XSearch?

Software engineers mainly, but anyone who has a large number of pure text files will benefit.

Searching a large amount of source code, across many directories, is both tedious, and time consuming. Think of this tool as a helper to finding that needle in a haystack!
How many times as a software engineer do you find it essential to search code looking for specific functions, or declarations within the source code? Now with XSearch, you can quickly look-up the code locations, and often get the info without having to open the file in your editor.