Break out docs into new structure, and add --man=faq and --man=cookbook options

[petdance]

I've found it very difficult to maintain docs in ack. We also need more granular docs.

Create a new doc structure App::Ack::Docs::*. To start with, we'll have

• App::Ack::Docs::Man -- current manual
• App::Ack::Docs::FAQ
• App::Ack::Docs::Cookbook -- A list of examples and recipes for using ack (I'm not set on the name "Cookbook")

All these docs will need to get put into the ack standalone. They'll get put at the end of the file during squashing.

The ack --man switch will now take arguments, so you can say ack --man=faq and ack --man=cookbook.

[petdance]

This may not work out so well. I'm looking into Pod::Usage and its rules. http://search.cpan.org/~marekr/Pod-Usage-1.69/lib/Pod/Usage.pm

[petdance]

@preaction uses this: https://metacpan.org/source/PREACTION/Beam-Runner-0.006/lib/Beam/Runner/Command/help.pm#L49-54

[petdance]

ack-standalone has to work on itself without loading any external .pm files.

Write a .t file to make sure --man and --faq work on both ack and ack-standalone.

[petdance]

Some options are loaded in ack, and some in App::Ack::ConfigLoader. Remove any extraneous stuff in ConfigLoader.

[petdance]

The docs have been broken out in 81ce3cd but there are still problems to fix.

1. Do we want to still have ack use perldoc for its rendering?

2. If so, how do we handle the tests that complain if someone's perldoc is not set up correctly?

t/ack-man.t is TODOed because of these questions.

[petdance]

Yes, we need to use perldoc / Pod::Usage.

[petdance]

This split-up form of manual also will help us with the ack3 redesign where we will have different HTML pages for different manual sections.

[petdance]

I have the --man, --faq and --cookbook working for ack-standalone, but ack-man.t fails.

[petdance]

Looks like perldoc isn't happy about the removal of $ENV{PATH}. Needs more exploration.

[petdance]

Remaining problems are now in #122.