Don't advertise that ack is a Perl module

[petdance]

I'm the creator of ack.

In the README for ack.vim, ack is described as "Perl module App::Ack” and "the Perl module / CLI script ‘ack’” I suggest dropping the part that it’s a Perl module, if not forgetting entirely that it’s Perl. I specifically don’t advertise ack as a Perl thing because I don’t want people to say “Perl? I don’t know Perl.” When Debian first packaged ack they were going to call it “perl-ack” or something like that, and I practically begged them to not call it that. If people later on discover that it’s Perl, that’s cool.

Also, many (most?) don't have ack installed as a module and are instead using the standalone version.

[ches]

Hi Andy, thanks for your interest in the plugin (and I'll try to get to responding to your other tickets).

It always felt a little funny to me too that the README highlights the Perl module name, as you say I think the great majority of people care foremost about using ack as a tool, not a library, especially when it comes to the Vim plugin.

I'm happy to change the text, and probably linking to https://beyondgrep.com/ in the intro makes more sense than CPAN. I'll come up with a rewording, unless you have something in mind to suggest.

[petdance]

I'm guessing that 90% of the ack users don't use it from CPAN.

Beyondgrep.com really needs a page dedicated to ack.vim. I've made a ticket about it. https://github.com/petdance/beyondgrep/issues/64

[petdance]

Also get the description of the project on the front GitHub page that says "Vim plugin for the Perl module / CLI script 'ack'"

[petdance]

[ches]

I can't actually edit that, I have merge/push rights but not full repository admin access to settings—that'll need to come from @mileszs. We might want to consider moving the project into an organization.

[petdance]

Probably not worth setting up an organization to make a 10-second change to the project. It's not a hurry.