The right way to do this is to set your Windows' font size. If you're using Windows 7, just open a "Windows Explorer" window, and enter for its address this: "Control Panel\Appearance and Personalization\Display" (without quotes). You can then get Windows to display fonts larger (say 150%).There's a reason for 2-space code format policy. Traditionally, it is to produce more compact code pages; having a printout showing wide tabs/indents will mean more paper to carry around for a given amount of code. But that is moot now, since we are "paperless". We need to respect the project owner's preference, given that it is reasonable, when it comes to code formatting. Personally, I think 4-space indents is better for most people (my eyes are keen, so I don't care).

There is no need to be insulting or rude. If you don't brand me a heretic for 3-space indents, I won't brand you one for insisting on ridiculously large margins and font sizes.

Actually, I believe the real reason for narrow newspaper columns is to disguise that they are written at a grade-5 reading level.

Pieter-----------------------------------------"Even on the attack, I found the spade [to be] the equal of the rifle." Erwin Rommel, Infantry Attacks

The right way to do this is to set your Windows' font size. If you're using Windows 7, just open a "Windows Explorer" window, and enter for its address this: "Control Panel\Appearance and Personalization\Display" (without quotes). You can then get Windows to display fonts larger (say 150%).There's a reason for 2-space code format policy. Traditionally, it is to produce more compact code pages; having a printout showing wide tabs/indents will mean more paper to carry around for a given amount of code. But that is moot now, since we are "paperless". We need to respect the project owner's preference, given that it is reasonable, when it comes to code formatting. Personally, I think 4-space indents is better for most people (my eyes are keen, so I don't care).

There is no need to be insulting or rude. If you don't brand me a heretic for 3-space indents, I won't brand you one for insisting on ridiculously large margins and font sizes.

Yikes! I must have expressed myself wrong! I didn't mean to be insulting at all!

But seriously, the right way to do it is to increase the Windows font size. I do that all the time with my smaller 21-inch monitors (am too used to 32-inch monitors when at home, good for eyes, won't cause strain which leads to myopia, I believe).

I'm not sure if we're on the same page regarding SVN (and other version-control) repository management. But there really are valid reasons for spaces (not tabs), as Joel had mentioned. These reasons are here to stay because most all of us have learned our lessons, and learned them painfully in most cases. A straightforward way to understand that painful lesson is this: anything that can be interpreted in more ways than one isn't written right. In short, such a thing is called "vague". For eg, a tab can be interpreted as 1-inch or 4-inches, depending on the editor.

Likewise, to further illustrate that "anything that can be interpreted in more ways than one isn't written right", and that also means "vague"... I'll attempt to apologize for any possibility that my message was rude or insulting. As can be seen, my message was possibly vague enough that it is construed as rude by you, though construed as well-meaning by myself. (That is, I meant to make things easier for Joel, as well as assist you in adjusting to a tried-and-true practice). And that's that! My previous message was a perfect example of a message that is just not right, since it can be interpreted in more ways than one!

If you're thinking that my explaining how to use Windows is being condescending, you should know that I just recently learned Windows 7! No, I never went to Vista. I stuck with WinXP and avoided Vista like the plague. I thought you might be as unfamiliar with Windows 7 as I am! Many people avoided Vista like the plague. Plus, I never was much good with Windows.

About 4-space indents, it actually is a norm for Java code. I don't know why. Maybe it has a reason tied to being Object-Oriented, not sure. I only know that most people I work with hate 2-space indents (except hardcore masochistic veteran coders, I think).

As for 3-space indents, I don't know why 2-space and 4-space were the norms in the first place. Maybe 2-space was better than 1-space, and the new exercise to "increase the indent" simply doubled the 2-space (equals 4-space) indent?

pgeerkens wrote:Actually, I believe the real reason for narrow newspaper columns is to disguise that they are written at a grade-5 reading level.

Oh. So that's why grammar errors are the norm there? Hmm. I always thought newspaper folks were rushed for time, and language mistakes were somewhat forgivable. Gosh, my grade-5 English must be bad. Even now, most words in newspapers are beyond me. (I'm not a native English-speaker, by the way).

Thus spake pgeerkens:> > Agreed that Notepad is suitable only for very quick and very dirty work,> given other choices, but it is occasionally useful. I once was a __vi__> pro, but that was almost before you were born. :D My finger still> understand h-j-k-l though.>

I use Vim more than any other single application. Why'd you stop usingvi?

Thus spake viewofheaven:> > "pgeerkens" wrote:> > I will remember harder to to only use tabs for block indentation, and> > not internal to a line.> > It will be fine if you set Eclipse to "convert tabs to spaces", then you> can tab all you want! That way, you can have all the spacing you want> (eg 4 spaces) within any line, between any code elements, which makes> for easier viewing.

If I understand what "convert tabs to spaces does", then this doesn'taddress Pieter's point. He'd like to have 3-space indentation, but thissetting will have no effect if there are no tabs in our files.

Thus spake viewofheaven:> > There's a reason for 2-space code format policy. Traditionally, it is to> produce more compact code pages; having a printout showing wide> tabs/indents will mean more paper to carry around for a given amount of> code. But that is moot now, since we are "paperless". We need to respect> the project owner's preference, given that it is reasonable, when it> comes to code formatting. Personally, I think 4-space indents is better> for most people (my eyes are keen, so I don't care).

My reason for 2-space indent is that it keeps indentation from becomingtoo deep too quickly. Two spaces is by far the most common indentationpolicy in code I see these days.

Thus spake viewofheaven:> > "uckelman" wrote:> > > > "viewofheaven" wrote:> > > The file for which I just submitted a suggested patch:> > > EnumeratedPropertyPrompt.java> > > > I checked this file from trunk@7961 in a hex editor and found no 0x0D> > anywhere. Where exacty is the \r you're seeing?> > Every single line! I used XVI32 (hex editor) to check it too, and found> the same thing that my Emacs showed me.> > Is anyone else seeing this? Is my TortoiseSVN doing a number on me? My> checkout of trunk shows a good 50% of files with CRLF and the other 50%> with LF. No mixture of CRLF and LF within any single file, though.>

I checked again just to be sure. I see no CRs there at all.

> "pgeerkens" wrote:> > I recently stumbled on some html files in the tree recently that must> > have had only LF after downloading> > This is a vital clue! On Windows 7 TortoiseSVN, a checkout does not seem> to auto-convert all line endings to anything else. On Windows 7 Cygwin> SVN, there __does seem__ to be an auto-conversion of line endings to LF.> So that could explain why Joel isn't seeing the CRLF on checkout?

I'm not using Cygwin. I'm not even using Subversion everywhere. I am for3.1, but for the trunk, I'm using git as a Subversion client. I see noCRs in either one.

> We should put up comprehensive code formatting policies, and HowTo(s)> (for various IDEs) to adhere to such policies. That should make it easy> for every developer to adhere to the code formatting policy.

Nothing against vi - I would still use it in the right circumstance, and have once or twice installed it (and sed) to windows - but I stopped working for companies that coded for UNIX. Also, the functionality gap between vi and other code editors narrowed.

Pieter-----------------------------------------"Even on the attack, I found the spade [to be] the equal of the rifle." Erwin Rommel, Infantry Attacks

Thus spake viewofheaven:> > "uckelman" wrote:> > I'm not using Cygwin. I'm not even using Subversion everywhere. I am> > for 3.1, but for the trunk, I'm using git as a Subversion client. I> > see no CRs in either one.> > Well, how about Windows 7 with TortoiseSVN? Have you checked that? I> really am sure there are CRLF in 50% of the files.

I can't, I don't have access to Windows 7.

> Anyway, I'll just commit my changes using LF for whatever files I'm> committing.> > Was just trying to give you a heads up regarding possible corruption of> line endings in SVN repos.

I appreciate the notice, but this should be ok, really, since every texteditor that anyone codes in can handle it.

viewofheaven wrote:Was just trying to give you a heads up regarding possible corruption of line endings in SVN repos.

I appreciate the notice, but this should be ok, really, since every texteditor that anyone codes in can handle it.

Actually, I was worried about inconsistent character codes (for line endings) in SVN repos. That could throw us some problems later on. At the least, it means a systemic irregularity that should be resolved, much like how "tabs must always be represented by spaces, or vice versa, all the time, choose one or the other".

Another file that has CRLF: PieceMover.java in package "VASSAL.build.module.map".