#667 Source Formatter should honor .perltidyrc in project root directory

[abhishekisnot]

By default, perltidy command will follow below precedences while formatting code:
1. command line options
2. .perltidyrc in current directory
3. .perltidyrc in user's home directory

But, from EPIC, perltidy command is executed from EPIC's script directory, which causes perltidy to not honor .perltidyrc from project root.

If SourceFormatter or ScriptRunner can fire the command from projects root directory, perltidy will honor project specific settings for perltidy.

NB: On testing branch, we pass below command line options, from IDE preferences:
perltidy -q --indent-columns=4 --maximum-line-length=120 --entab-leading-whitespace=4

[Oliver Trosien]

@jploski what about reading/writing the perltidy settings into a project root .perltidyrc? This would avoid contradicting settings between perltidy on command-line and perltidy called from epic. perltidyrc is also respected from other tools, like this perlcritic rule:
http://search.cpan.org/dist/Perl-Critic-1.123/lib/Perl/Critic/Policy/CodeLayout/RequireTidyCode.pm