unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@member.fsf.org>
To: emacs-devel@gnu.org
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	[thread overview]
Message-ID: <85boe9tayd.fsf@member.fsf.org> (raw)
In-Reply-To: <jwvvcchx44o.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 04 Dec 2012 09:51:58 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> 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
http://www.gnu.org/prep/standards/standards.html

-- 
-- Stephe



  parent reply	other threads:[~2012-12-05  3:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Tf2rc-00087q-Kb@vcs.savannah.gnu.org>
2012-12-02 23:58 ` /srv/bzr/emacs/trunk r111061: Fix for bad test in ruby-mode-tests.el Dmitry Gutov
2012-12-03  4:13   ` Chong Yidong
2012-12-03 18:45     ` Dmitry Gutov
2012-12-03 19:48       ` Stefan Monnier
2012-12-03 19:55         ` Burton Samograd
2012-12-03 21:03           ` Dmitry Gutov
2012-12-03 21:20             ` Burton Samograd
2012-12-03 21:54           ` Stefan Monnier
2012-12-03 20:00         ` Dmitry Gutov
2012-12-04  8:44         ` Stephen Leake
2012-12-04 14:51           ` Stefan Monnier
2012-12-04 17:55             ` martin rudalics
2012-12-04 18:07               ` Stefan Monnier
2012-12-05  9:41                 ` martin rudalics
2012-12-05 14:54                   ` Stefan Monnier
2012-12-05  3:49             ` Stephen Leake [this message]
2012-12-05  4:56               ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=85boe9tayd.fsf@member.fsf.org \
    --to=stephen_leake@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).