| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2018-12-05 | revise perltidyrc | Perl Tidy | 1 | -0/+4 | |
| 2018-10-02 | no bug - adopt mojolicious code formatting guidelines (#784) | Dylan William Hardison | 1 | -3/+13 | |
| @kyoshino likes 2-char indent for all the frontend. Mojolicious seems to use 2-space too. Let's just adopt their perltidyrc. Included in this is a script (in scripts/) that will modify files according to these rules. | |||||
| 2017-07-14 | replace perltidyrc with on that specifies -pbp with two exceptions | Dylan William Hardison | 1 | -16/+3 | |
| previously, the perltidyrc was written with the original recommendations of the upstream bugzilla project. The style used there is... inconsistent at best. For a while now, I've been using perltidy -pbp and telling others to do the same for new code. However there are two exceptions to -pbp that are widely useful: 1. line length can be up to 120. 2. brace vertical tigntness is turned off. This means that there is always a newline after the { in a multi-line brace construct. | |||||
| 2014-09-22 | Fix typo in new .perltidyrc | Dylan William Hardison | 1 | -1/+1 | |
| 2014-09-22 | Bug 1060728 - Add perltidyrc that makes it easier to follow existing code ↵ | Dylan William Hardison | 1 | -0/+16 | |
| standards to BMO repository | |||||
 |
index : bugzilla | |
| Bugzilla | Florian Pritz |
| summaryrefslogtreecommitdiffstats |
path: root/.perltidyrc