git misery
 

I just tried to pull the latest changes in angbandbase, and got conflict errors for every single file. It looks like a UNIX/WINDOWS EOL problem.
Any suggestions on how to fix it, with either the UI or the command line?

Use linux :)

Seriously, no, I'm afraid - I haven't got a good Windows git client yet, but I haven't really been trying.

Pete, what editor on Windows are you using?

One thing to try is to use an editor which can save unix line endings, try saving the affected files with different line endings and see how that works.

Can you tell if the problem is that you have locally changed the endings on a bunch of lines, or if the remote source (i.e. Nick) has changed the endings on a bunch of lines?

If you have vim installed (like I do), use it to smash the line endings into the non-conflicted form.

I believe the desired vim command is

:%s/^v^m//

Where ^v should be interpreted as "control + v" and ^m as "control + m".

At least, that's what I've used in the past when poking at the NPPAngband source, and I'm pretty certain that the NPP devs are using Windows.

I understand all that, and I am using vim for that reason, but it's complaining about files I never even edited!
Grrr....
I never had problems like this with svn or even cvs :mad:

Maybe this will help?

http://help.github.com/dealing-with-lineendings/

@d_m
That's better, but I am still getting errors.

What's the correct command for syncing with source?
Once I figure this stuff out, I'm going to blow away my entire tree, then start over.

If you're going to blow it all away anyway, I'd recommend making your own fork of angband/angband on github, then cloning that locally. takkaria has just updated the instructions for usehere - written in small words for people like me :)