Commands using perl

Please note that binary file checking is NOT perfect.

So, use it with caution.

It does not delete hidden files whose name has a leading '.' character.

And it regards an empty file as a binary file.

Ever wanted to get the directory content with 'ls' or 'find' and had to wait minutes until something was printed? Perl to the rescue. The one-liner above(redirected to a file) took less than five seconds to run in a directory with more man 2 million files. One can adapt it to e.g. delete files that match a certain pattern.

A space-padded version:

Let -p do it's voodoo and do absolutely nothing but set the output record separator :-)

The dates in the output are Start Date, End Date, Days Remaining in warranty, respectively. This will only work if you are running it on a dell machine. You can substitute the dmidecode command with a service tag if you are not using a dell. Also, you have to either allow your user to run sudo dmidecode with no password or run this command as root.

Reads stdin, and outputs each line only once - without sorting ahead of time. This does use more memory than your system's sort utility.

This works by reading in two lines of input, turning each into a list of one-character matches that are sorted and compared.

This uses Text::Highlight to output the specified Perl file with syntax highlighting. A better alternative is my App::perlhl - find it on the CPAN: http://p3rl.org/App::perlhl

I used curl instead of lynx.

Cool but useless.

There are some environments that use this value for password and account expiration. It's helpful to be able to quickly determine the number of days since the Unix epoch (dse) when working directly with the configuration files as an administrator.

Nobody wants the boss to notice when you're slacking off. This will fill your shell with random data, parts of it highlighted. Note that 'highlight' is the Perl module App::highlight, not "a universal sourcecode to formatted text converter." You'll also need Term::ANSIColor.

The above one-liner could be run against all HTML files in a directory. It renames the HTML files based on the text contained in their title tag. This helped me in a situation where I had a directory containing thousands of HTML documents with meaningless filenames.

perl-based version

Not really better - just different ;)

There's probably a really simple solution out there somewhere...

If you are in an environment where you don't have the base64 executable or MIME tools available, this can be very handy for salvaging email attachments when the headers are mangled but the encoded document itself is intact.

Fun idea! This one adds seconds and keeps running on the same line. Perl's probably cheating though. :)