ack

For me ack is essential kit (its aliased to a and I use it a million times a day). Mostly it has everything I need so I'm figuring that this behavior is covered and I just can't find it. I'd love to be able to restrict it to specific kinds of files using a type. the problem is that these files have a full filename rather than an extension. For instance I'd like to restrict it to build files for buildr so i can search them with --buildr (Similar would apply for mvn poms). I have the following defined in my .ackrc --type-set=buildr=buildfile,.rake The problem is that 'buildfile' is the entire

From the ack installation page (http://betterthangrep.com/install/) there is a one-liner installation with curl: curl http://betterthangrep.com/ack-standalone > ~/bin/ack && chmod 0755 !#:3 I understand that it's getting the file from the website and saving it to ~/bin/ack, then setting permissions, but what does that last part ( !#:3 ) do ? (I do not recognize the syntax and Googling didn't yield any helpful results) See the section called HISTORY EXPANSION in man bash, particularly the Word Designators subsection. !#:3 refers to the third word of the pipe, which is (in your example) ~/bin

I have a problem with using ack-grep with a negative look ahead. I am running this command: ack-grep "paypal_responded(?!_at)" but I am getting the error: bash: !_at: event not found I have tried adding backslashes in various places, but I'm also new to using ack & linux, so please treat me as a newbie with any instructions. Thanks in advance. Try ack-grep 'paypal_responded(?!_at)' You need single-quote to avoid bash interpret ! as history expand command. The shell is interpreting the ! in your input as a command substitution: $ ack-grep root /etc/passwd root:x:0:0:root:/root:/bin/bash $ !ac

I put this in my .ackrc: --type-set=DUMB=*.orig --noDUMB ... but I'm still seeing files like main.py.orig in my ack results. I tried doing --type-set=DUMB=*.*.orig too, but that didn't work either. More info Run from my command line (OSX Snow Leopard with : timmfin at lorien in ~/dev/performable/rafa on landing-pages-csv-and-more! ± ack modules --python | grep '.orig' src/rafa/main.py.orig:25:import rafa.ui.modules.helpers src/rafa/main.py.orig:26:from rafa.ui.modules.performable_form import PerformableForm src/rafa/main.py.orig:27:from rafa.ui.modules.page_form import PageEditForm src/rafa

Say I'm designing a tool that would save code snippets either in a PostgreSQL/MySQL database or on the file system. I want to search through these snippets. Using a search engine like Sphinx doesn't seem practical because we need exact text matches of code when searching code. grep and ack and has always worked great, but storing stuff in a database makes a large collection of stuff more manageable in certain ways. I'm wonder what the relative performance of running grep recursively over a tree of directories is compared to running a query like SQL's LIKE or MySQL's REGEXP function over an