From: Jeff D. <da...@da...> - 2001-09-17 16:51:20
|
On Sep 16, 2001, Steve Wainstead said: > > Hmm. The page states: "Use an indent of 4 spaces, with no tabs. If you use > Emacs to edit PEAR code, you should set indent-tabs-mode to nil." So the > intention is to do away with tabs altogether, I suppose. If you need to > put tabs in the code then \t is the way to go. However I'm in a flexible > mood today... > > I'm willing to concede this point for the greater good of the project: if > everyone is happy with tabs, and adjusting your editor accordingly, we'll > go with tabs and I'll have to fix my .emacs file. To restate and (hopefully) clarify once again: My only beef is with tab-width=4. Setting indent-tabs-mode to nil is, I think, a fine way to go. But even with that setting, it's almost inevitable that some real tabs will make their way into the source code. (The PEAR source code demonstrates this quite well.) I just think those tabs that do make it into the source code should always be rendered as eight-space tabs, rather than funky four-space tabs. Here's what I'm proposing we use: // Local Variables: // mode: php // tab-width: 8 // c-basic-offset: 4 // c-hanging-comment-ender-p: nil // indent-tabs-mode: nil // End: If we include the above cruft in our source code, then you (probably) don't even need to fix your .emacs. Jeff |