From mboxrd@z Thu Jan  1 00:00:00 1970
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20020612180513.5392819A62@mail.cse.psu.edu>
Date: Wed, 12 Jun 2002 13:56:16 -0400
Topicbox-Message-UUID: aa7e55ae-eaca-11e9-9e20-41e7f4b1d025

// Shouldn't the editor promote... the One True Brace Style ?

in breif, no.

while i'm as much a fan of the style you've likely got in mind as i
imagine most people here are - IN C - it's not universal. as my
interjection there should have prompted, the first concern is that
i'm not always writing C. heck, i don't know about others here, but
_i'm_ not always writing _code_! i use Acme for pretty much all my
text editing needs, from coding to scratch notes to documentation
to printed letters to humans, to email. as often as not (at least),
imposing the One True Brace Style would be more of a burden than a
win. and that says nothing of languages that have differing styles
of syntax. i can only imagine how awkward using the auto-indent
style you're proposing would make programming in some of the
APL-like matrix/array math languages.

and, of course, there's the less theoretical, more practical
concern that pretty much every auto-indent system i've seen gets
things horridly wrong when faced with non-standard use, where
non-standard includes such wild and exotic things as cutting and
pasting code.

i'd further note that acme's brace matching makes it quite easy
to simply write your code ignoring the first tab and injecting it
later. and _surely_ (hopefully?) you're not advocating that the
editor understand the _language_, and impose auto-indenting
"features" on things like statements after if, for, etc.?
anothy