[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: /srv/bzr/emacs/trunk r111061: Fix for bad test in ruby-mode-tests.el

From: Stephen Leake
Subject: Re: /srv/bzr/emacs/trunk r111061: Fix for bad test in ruby-mode-tests.el.
Date: Tue, 04 Dec 2012 22:49:30 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (windows-nt)

Stefan Monnier <address@hidden> writes:

>> Which is why there needs to be a clear policy, supported by Emacs tools,
>> that everyone knows and follows.
> And the policy is: don't modify TABs or spaces on lines you do
> not otherwise change.

That's clear.

But the other part of the question was: are we supposed to use tabs or
spaces when editing new or old code?

It's easy enough to tell Emacs which to use, and it's best if all code
in a project follows a common standard.

I don't see any documentation on this in the various READMEs in the
Emacs source tree (but I may have missed something).

I thought this was mentioned in the Gnu coding standards (I have a note
in my .emacs for C style that says the Gnu coding standard requires tabs),
but I don't see it in the current version at

-- Stephe

reply via email to

[Prev in Thread] Current Thread [Next in Thread]