petdance / betterthangrep Goto Github PK

Maybe if I add the banner in the upper right corner people will send me website patches.

And maybe I should explicitly ask people to do so.

On the "Why ack?" page, part 9, it says "inensitive" when it should be "insensitive"

Hi, all

I'd like to recommend to you the beagrep tool, which combines a search
engine (beagle) together with grep.

Most programmer's searching needs are based on full words instead of
partial words, i.e., they search for "readlink", instead of
"readli.*". And search engines are very good with whole word file search
(although I needed to tune beagle so that it sotpped treating "stop" and
"stopped" as the same), so the idea is very simple: query beagle first,
and run grep only on the positive matching files only.

On Android source code, running grep alone on the whole source tree took
me more than half an hour before I hit Ctrl-C, using beagrep, it only
took half a second.

For more details, check out my github page: http://baohaojun.github.com/beagrep.html

A great lightning talk by @theaboutbox

http://www.youtube.com/watch?v=sKmyl5D8Da8

The old BTG.com had a link to the changelog on the front (and only) page. We're missing that. Somewhere we need an easy way to get the source to ack and see the changelog.

From Greg Houston [email protected]

You may want to add the Chocolatey Nuget install of Ack to your install page at http://betterthangrep.com/install/

Chocolatey is a package manager for Windows.

Here is the page for installing Ack using Chocolatey:  http://chocolatey.org/packages/ack

https://bitbucket.org/eliben/pss

I've had two emails in the past three days saying roughly this:

What:
Incorrect macport command

Wrong:
Port "perl/p5-app-ack"

Right:
port install p5.12-app-ack

So clearly my intent of saying "This is the name of the port" is unclear because people are taking it as install command. So fix that.

This ticket in the main ack project beyondgrep/ack1#42 raises the issue of "It's in the man page, but I prefer to read online". We ought to have the full ack docs somewhere online.

There's a list of 5 things on the front page, and they're vague and have pretty icons.

There's a list of 10 things on the "Why ack?" page, which are more specific and have no icons.

Somehow combine these two lists, preferably freeing up a page for other use.

http://blog.kowalczyk.info/software/vack/

So much confusion is out there because the Debian folks repackaged ack as ack-grep. Put up a page of FAQs and solutions to problems.

(Sorry, hope this is the appropriate way to use issues.. I'm new to github & OSS in general)

Can I propose that we split everything into two pages, 'homepage' and 'documentation' (possibly renamed 'help'):

• Homepage
  • Why use ack?
    • Top 10 reasons to use ack
    • Testimonials
  • How to get ack
    • How to install
    • ack for Textmate users
  • Mailing list signups
• Documentation
  • Manual
  • FAQ
  • Ack's command flags
  • Ack's recognized filetypes

There would be a big button the top of the homepage for those who want to skip the marketing stuff and just scroll straight down to the "How to get ack" section.

/documentation/man.html is just a pod2html dump of ack. There is no tracking, and there's no Google Analytics on it.

Can I use this somehow?

http://www.warrenellis.com/?p=14655

Screenshots make everything come alive!

https://lh3.googleusercontent.com/-oOZJZ7f-xng/Tri1p3Bjf1I/AAAAAAAAABk/RO72Z-BFVwI/s903/Screen+Shot+2011-11-07+at+10.50.28+PM.png

Whee!

We need more!

Links to other handy helpful sites:

• bobby-tables.com
• htmlparsing.com
• petdance.com
• book
  etc etc

https://github.com/djanowski/ack-tutorial

That's got a lot of goodness we could put live on the site.

Maybe the Testimonials page and Features pages have a sidebar link to Installation, for example.

Chris Jerdonek writes:

I'd like to suggest that the ack web site include instructions on how to file a bug report. I can't seem to find instructions on the web site.

In particular, should bug reports be sent to the users list or posted as an issue on GitHub? The web site doesn't seem to mention the GitHub site, by the way.

This article by @nelstrom should go on the articles page.

http://vimcasts.org/blog/2013/03/combining-vimgrep-with-ack--f/

Take the big Bill The Cat logo from the front of the site and make a suitable favicon.ico.

I have far more traffic to BTG than Perlbuzz + petdance.com combined. Point to these sites to get some cross traffic.