Hi Gerhard,

Here's the string we use:

'-l=100 -i=4 -ci=4 -vt=0 -vtc=0 -cti=0 -pt=1 -bt=1 -sbt=1 -bbt=1 -nsfs -nolq 
-bbao -nola -ndnl'

I'll add it to the developers documentation.
By the way, since mid August we use Perl::Tidy in the CVS checkin process, 
which means that every commit is automatically 'tidied'.

((enjoy))
-
Michiel Beijen
R&D
 
OTRS AG
Norsk-Data-Str 1.
61352 Bad Homburg
Germany
 
T: +31 (0) 6457 42418
F: +49 (0) 9421 56818-18
I:  http://www.otrs.com/
 
Business Location: Bad Homburg, Country Court: Bad Homburg, Commercial 
register: 10751, Tax ID: 003 240
97505 Chairman of the Board: Burchard Steinbild, Managing Board: André 
Mindermann (CEO), Martin Edenhofer
 
CU@ CeBIT 2010 in Hannover (Germany) and get to know more about OTRS at booth 
no. C37, in hall 2 from March 2-6, 2010! bit.ly/7uyQfY



On Fri, 2009-12-11 at 20:12 +0100, Gerhard Weber wrote: 
Hi everybody.

I'm looking for the perltidy settings used in the perl modules of OTRS.
I looked on otrs.org, FAQ, docs and google but didn't find anything
usefull.
Only the occasional sentence "Log Message: Code cleanup with PerlTidy".

Can anybody post the settings or an .perltidyrc file?

Thanks in advance,
gerhard

--------------------------------------------
Thus spake the master programmer:
"Though a program be but three lines long, someday it will have to be
maintained."


---------------------------------------------------------------------
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
---------------------------------------------------------------------
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev

NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/

Reply via email to