From: Steve Klabnik <steve@...>
Date: 2011-05-17T22:05:47+09:00
Subject: [ruby-core:36268] Re: Whitespace conventions?

--000e0ce0b19a18ac7504a3786e4a
Content-Type: text/plain; charset=ISO-8859-1

>
> If you use Emacs or Vim, I wrote a guide:
> http://redmine.ruby-lang.org/projects/ruby/wiki/DeveloperHowto#coding-style



Right. So this seems to imply that at least the Ruby shouldn't have any
tabs, so I'll take care of that, at least. Seeing a line that starts with
"space space tab space space" makes me cry...

As for the C, well, personally, I now code my C with two spaces, but I also
recognize that that's unusual. While historically, C has been 8 spaces to a
tab, I think that I've seen more code in the wild with 4.

I personally prefer the 'exapandtab religion' because it ensures that the
source looks good when people look at it, and it looks the exact same for
everyone who's working on the code. We already acknowledge that wrapping to
80 columns is a good idea, and tabs seems like the same thing to me. You
either let everything be define-able by everyone, or you pick something for
everyone.

Then again, I'm new around here, and I haven't really done any work on the C
yet, so I really care more about the Ruby that I'll be working on, at least
at first.

Will you say the same thing when you contribute to GNU?


I would not contribute to GNU code for a host of reasons, but the incredibly
ugly coding conventions is one of the minor ones. Ruby is all about making
programmers happy, not making it easy to write plugins for Emacs that
manipulate code.

--000e0ce0b19a18ac7504a3786e4a
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">If you use Emacs=
 or Vim, I wrote a guide:<br>
<a href=3D"http://redmine.ruby-lang.org/projects/ruby/wiki/DeveloperHowto#c=
oding-style" target=3D"_blank">http://redmine.ruby-lang.org/projects/ruby/w=
iki/DeveloperHowto#coding-style</a></blockquote><div></div></div><br><div>
<br></div><div>Right. So this seems to imply that at least the Ruby shouldn=
&#39;t have any tabs, so I&#39;ll take care of that, at least. Seeing a lin=
e that starts with &quot;space space tab space space&quot; makes me cry...<=
/div>
<div><br></div><div>As for the C, well, personally, I now code my C with tw=
o spaces, but I also recognize that that&#39;s unusual. While historically,=
 C has been 8 spaces to a tab, I think that I&#39;ve seen more code in the =
wild with 4.</div>
<div><br></div><div>I personally prefer the &#39;exapandtab religion&#39; b=
ecause it ensures that the source looks good when people look at it, and it=
 looks the exact same for everyone who&#39;s working on the code. We alread=
y acknowledge that wrapping to 80 columns is a good idea, and tabs seems li=
ke the same thing to me. You either let everything be define-able by everyo=
ne, or you pick something for everyone.</div>
<div><br></div><div>Then again, I&#39;m new around here, and I haven&#39;t =
really done any work on the C yet, so I really care more about the Ruby tha=
t I&#39;ll be working on, at least at first.</div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margin=
-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color=
: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Will you say the same thing when you contribute to GNU?</blockquote><div><b=
r></div><div>I would not contribute to GNU code for a host of reasons, but =
the incredibly ugly coding conventions is one of the minor ones. Ruby is al=
l about making programmers happy, not making it easy to write plugins for E=
macs that manipulate code.=A0</div>
<span class=3D"Apple-style-span" style=3D"font-family: arial, sans-serif; f=
ont-size: 13px; border-collapse: collapse; "><br><div></div></span>

--000e0ce0b19a18ac7504a3786e4a--