Thomas Frössman

As an inital attempt i thnik I'm gonna go with adding an ag-pt-\* infix versionx of all defcustoms that refer to specifically to ag and one for choosing which searcher...

I know. The current ag- namespace makes things a bit confusing, to really do this proper renamespacing into alloy- and would make things less confusing.. An alternative would be to...

the differences at a basic level are not that big when taking a quick look though...  The first command is what ag.el currently...

An alternative way to handle both searches could be to detect if ag-executable is set to pt and then filter arguments that pt does not support. That solution is depending...

ok,. there already is a pull request for adding --literal https://github.com/monochromegane/the_platinum_searcher/pull/27 So maybe it's better for me to focus on adding (or lobbying if I'm lazy) --column as well to...

Implementing the column part of the matching in elisp might also be viable solution if it isn't too slow. I'll start a discussion at the other end of this as...

yeah, but it lacks most or all features of ag.el

I've implemented a from my viewpoint suitable --column implementation now which I hope will be merged.. So now onto the ag.el pt part.. .. I've just quickly looked at how...

I did think of how to properly support pt in ag.el, just now while taking a shower :) It's probably a good idea to structure the solution from a viewpoint...

AG however does not work well with windows when I tried it sometime in the past.. Also PT being a go program it's very easy to install from source regardless...