Alright, i am if not convinced then at leadt outnumbered. :-) Let me
do some tests with the merges and I will make a new release shortly
and then do the perltidy.
--
http://localrobot.com/
On May 12, 2010, at 9:03, Charlie Brady > wrote:
+1
On Wed, 12 May 2010, Robin Bowes wrote:
> On 12/05/10 07:00, Ask Bjørn Hansen wrote:
> >
> > On May 11, 2010, at 21:25, Robert Spier wrote:
> >
> >> Does anyone else have any opinions on doing a massive perltidy?
> >> I'm on the fence.
> >
> > I'm on the fence, too. My concern is mostly for
On May 11, 2010, at 11:00 PM, Ask Bjørn Hansen wrote:
> On May 11, 2010, at 21:25, Robert Spier wrote:
>
>> Does anyone else have any opinions on doing a massive perltidy? I'm
>> on the fence.
>
> I'm on the fence, too. My concern is mostly for the people with private
> patches / hacked up
On 12/05/10 07:00, Ask Bjørn Hansen wrote:
>
> On May 11, 2010, at 21:25, Robert Spier wrote:
>
>> Does anyone else have any opinions on doing a massive perltidy?
>> I'm on the fence.
>
> I'm on the fence, too. My concern is mostly for the people with
> private patches / hacked up versions. (
On May 11, 2010, at 21:25, Robert Spier wrote:
> Does anyone else have any opinions on doing a massive perltidy? I'm
> on the fence.
I'm on the fence, too. My concern is mostly for the people with private
patches / hacked up versions. (Maybe that makes less sense than I think it
does).
Ho
On 12. mai 2010, at 06.25, Robert Spier wrote:
> Does anyone else have any opinions on doing a massive perltidy? I'm
> on the fence.
I say: Do it.
-J
Does anyone else have any opinions on doing a massive perltidy? I'm
on the fence.
At the very least I'd go for the equivalent of a M-x untabify, but at
the point you're doing that, it's almost worth going all the day.
-R
On May 9, 2010, at 11:42 PM, Robert Spier wrote:
> Assuming
> http://github.com/msimerson/qpsmtpd/commit/6948c27205ebdec045604bd8d6bf6a3a04c35a8a
> is the output of this experiment...
Tis true.
> If we were to just fix the "big issues", I think that would help most
> places without causing the
On May 9, 2010, at 11:42 PM, Robert Spier wrote:
Assuming
http://github.com/msimerson/qpsmtpd/commit/6948c27205ebdec045604bd8d6bf6a3a04c35a8a
is the output of this experiment...
I'm not convinced that "one big" tidy is actually worth the
hassle/mess.
Do we peel off the bandaid slowly, or ju
Assuming
http://github.com/msimerson/qpsmtpd/commit/6948c27205ebdec045604bd8d6bf6a3a04c35a8a
is the output of this experiment...
I'm not convinced that "one big" tidy is actually worth the
hassle/mess.
If we were to just fix the "big issues", I think that would help most
places without causing t
On Fri, 3 Apr 2009, Jared Johnson wrote:
Both nbbc and msc relate to perltidy adding whitespace to set apart comments.
[-nbcc], -bbc, --blanks-before-comments
A blank line will be introduced before a full-line comment.
This is the default. Use -nbbc or --noblanks-before-c
Both nbbc and msc relate to perltidy adding whitespace to set apart
comments.
[-nbcc], -bbc, --blanks-before-comments
A blank line will be introduced before a full-line
comment. This is the default. Use -nbbc or
--noblanks-before-comments to prevent such blank lines from
Matt Sergeant wrote:
On Fri, 3 Apr 2009 08:38:59 -0500, Jared Johnson wrote:
first of all, kudos on the frequent releasing :)
I've attached a suggested patch to .perltidyrc. I've been playing
around with perltidy'ing all QP code and some results I don't like.
This doesn't fix all the things
On Fri, 3 Apr 2009 08:38:59 -0500, Jared Johnson wrote:
> first of all, kudos on the frequent releasing :)
>
> I've attached a suggested patch to .perltidyrc. I've been playing
> around with perltidy'ing all QP code and some results I don't like.
> This doesn't fix all the things that I don't l
[-nbcc], -bbc, --blanks-before-comments
typo'd my interposition there, it's -nbbc
-Jared
15 matches
Mail list logo
