Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 70070 invoked from network); 2 Jun 2010 21:23:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Jun 2010 21:23:22 -0000 Received: (qmail 74807 invoked by uid 500); 2 Jun 2010 21:23:22 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 74778 invoked by uid 500); 2 Jun 2010 21:23:22 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 74770 invoked by uid 99); 2 Jun 2010 21:23:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 21:23:22 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hirsch.dick@gmail.com designates 72.14.220.152 as permitted sender) Received: from [72.14.220.152] (HELO fg-out-1718.google.com) (72.14.220.152) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jun 2010 21:23:16 +0000 Received: by fg-out-1718.google.com with SMTP id 16so145076fgg.0 for ; Wed, 02 Jun 2010 14:22:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=Voyax+R7wJY4hD04M+lTCpO9ciIb3HBfYAaq3alSrSU=; b=xYgUPM+Z+ymqylUf//bMAm+tAI4lGm9ZwzwbG7Om7Odt/Qp5rwsLfh42/nA4epHypc 99jdz7i9f5SRd2vWXFmbYoOwDG++v9mUCO5J1xSOyU10DRghOIQx8tygv3uKdyTPaBJ4 PAv5v8uVZK5+h9+uVo34Jt2UOFSnFKlrd/1bQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=nPxRlHJrRD4U8dFbzZUfxBBwGzD8zdtZ28pBFM5PDp3NkQttbXyGGVncFasJhD0nn0 Vj7apj7Cl2o9Z+Qf6poQn08FkyU3ud52NcHfMtmiH29uUToT4jH9dlwSJbTyqTsCqU7x oQnE3RpaWXhMEwUVjbAV5yWSPMedsKBipVkug= MIME-Version: 1.0 Received: by 10.102.254.26 with SMTP id b26mr3161339mui.118.1275513775965; Wed, 02 Jun 2010 14:22:55 -0700 (PDT) Received: by 10.103.239.5 with HTTP; Wed, 2 Jun 2010 14:22:55 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Jun 2010 23:22:55 +0200 Message-ID: Subject: Re: Style conventions From: Richard Hirsch To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org How did you indent? Manually or with a tool? I've been experimenting with Scala Formatter in Eclipse but it doesn't always work correctly. D. On Wed, Jun 2, 2010 at 10:56 PM, Vassil Dichev wrote: > I just took the liberty of formatting a couple of files (API2, > API2Test and AuthToken) which looked just... wrong in my editor. The > reason was that some lines were indented using tabs, while the Scala > convention (used in the rest of the ESME files) uses 2 spaces for > indentation. > > We posted a Scala Style guide some time ago > (http://davetron5000.github.com/scala-style/), it would be really > helpful if we could stick to it! In order to do so, it is necessary > that our editors/IDEs are set up to respect this convention and not > apply formatting which might surprise others. > > Sorry for the nitpick, but documents with mixed tabs/spaces, while > they look perfectly OK on editors with the "correct" tab size, produce > horrendous results in editors with a different indentation setting. > > Vassil >