Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

ack 1.70 adds context and line-specific matching 5 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Thank you for ack. Thank you doubly for ack-standalone!
    • You're very welcome. Do you just toss the ack-standalone in your ~/bin dir and carry it around? Or is there another reason it's a ++ ?
      --

      --
      xoa

      • This is the first I had heard of the standalone version. Previously I only had ack installed on my personal system because I am reluctant to do system level installs on any of our servers and I've never had any luck with user-directory cpan installs.

        So, I just copied ack-standalone into ~/bin on one of the servers and it worked great.
        • That's why I have it like that. I think I'm going rename it to ack-single-script or maybe ack-no-dependencies so people notice it more. If you don't have your ~/bin directory in Subversion, do so. Makes it even easier to have everything synced between your machines. The way I do it is documented at http://xoa.petdance.com/How_to:_Keep_your_home_directory_in_Subversion [petdance.com].
          --

          --
          xoa

          • If others are anything like me, then the problem isn’t that people don’t figure out what “standalone” means, it’s that they install ack from CPAN and never bother to look at its website (let alone the Google Code project). But there is no mention of ack-standalone whatsoever in the distro docs (ie. the parts that search.cpan.org exposes prominently), save for a passing one in the Changes. Not even the installation instructions in the README say anything about it. I knew it exists only because I saw a post of yours mentioning it somewhere on some mailing list.

            If you want people to notice it, advertise it in the README and the POD.

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.