From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by hurricane.the-brannons.com (Postfix) with ESMTP id 7F1C477892 for ; Thu, 30 Jan 2014 07:09:25 -0800 (PST) Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta08.westchester.pa.mail.comcast.net with comcast id LD5Z1n0010SCNGk58F91kX; Thu, 30 Jan 2014 15:09:01 +0000 Received: from eklhad ([107.5.36.150]) by omta09.westchester.pa.mail.comcast.net with comcast id LF911n00U3EMmQj3VF91Gh; Thu, 30 Jan 2014 15:09:01 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.4.10 Date: Thu, 30 Jan 2014 10:09:01 -0500 Message-ID: <20140030100901.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391094542; bh=+DKJaKa6lm7xnqY5nWJwGBWK/b2nHZc4+PG76I0/4JA=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=jXSemfeFmrLMmzh+Ptfdkt3Mz4E2i/SwBc3xxv0dEkJJOHidzCCb0NRBezyUujsZS Pm19sePvfQ7l2CbgU/JQS7/aFEWBgXbmMcfZq+R85uwP3F8gr50aBFVSUyNPlIz35B V6GEnjE2D1A374swYaA8XSyAefPtlRMR3X3F1nff6QIIOoW7XC5eSA7j+Qse8JFAZw ud8T3YG5LC31urphaH4JutkYW5iilY1vgC1GUKDkYrKGfl1kCeZbK/+4h7XKFOKsff s/bRaYnNfG/pqOiVFbiuYKlu9FAbC8l4uO4gBnk+TfuUZiyyzlnc/dtQt1Z5qdnoWC 3TV4Hik4MTt6g== Subject: [Edbrowse-dev] indenting X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 15:09:25 -0000 I almost don't care, so if other people do that will win the day. Would you prefer a different style of indenting? I came up with this one over ten years ago, but now I really don't like it, because of the mix of spaces and tabs. Guess I was trying to prevent really long lines, so only indent by 4. Well the way to prevent long lines is by programming better. Linux kernel indents by tabs, by blocks of 8 spaces, and all the braces and other styles I like too. Would we be better off using their indent script, or maybe some other script? I just like being able to list a line and count tabs and know the indent, like when I work in the kernel, but edbrowse source doesn't work like that. If you have kernel source look at scripts/Lindent. Indenting by tabs is pretty much the standard. Also I wonder if we should not run eb.h through such a script. It's just externs and defines. And now with the extern C { } around it, everything is indented for no reason. It's just a little awkward / confusing. Karl Dahlke