>> Indeed, but I guess we should go with Emacs' conventions. The >> question then is, of course, if we should pro-actively convert our >> files. One strategy would be to convert one file after the other >> when one touches it anyway, probably in a seperate commit. At least >> we should try not to have a file half tab-indented and the other part >> space-indented. > > I'm not sure, but I think the latter strategy is the one chosen by > Emacs project. IIRC the rationale was not to produce large portion of > history tracked which is just replacement of tabs with whitespaces. > But that concern doesn't apply to AUCTeX. I would be fine if we just > `untabify' AUCTeX sources and check them in a separate commit. > > What do others think?
Yes, I think that's ok for us, and I'm going to do that right now. And diffing across tab/space indentation boundaries is not so painful with git (see the various --ignore-*-space options). Bye, Tassilo
