9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: anothy@cosym.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Emacs
Date: Wed, 12 Jun 2002 13:56:16 -0400	[thread overview]
Message-ID: <20020612180513.5392819A62@mail.cse.psu.edu> (raw)

// 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


             reply	other threads:[~2002-06-12 17:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12 17:56 anothy [this message]
2002-06-12 20:37 ` [9fans] Brace style - an acme how-to Fariborz Tavakkolian
  -- strict thread matches above, loose matches on Subject: below --
2002-06-12  9:18 [9fans] Emacs nigel
2002-06-12  9:07 forsyth
2002-06-12 10:08 ` John Murdie
2002-06-13  9:29 ` Don
2002-06-12  7:49 Fco.J.Ballesteros
2002-06-11 10:08 forsyth
2002-06-12  8:54 ` Don
2002-06-10 10:31 nigel
2002-06-10 10:31 nigel
2002-06-10 10:21 Fco.J.Ballesteros
2002-06-10 10:10 forsyth
2002-06-07  9:35 nigel
2002-06-10  9:53 ` Blake McBride
2002-06-10 17:00   ` Steve Kilbane
2002-06-11  9:08   ` Don
2002-06-11 18:55     ` Vladimir G. Ivanovic
2002-06-12  8:54       ` Don
2002-06-11  9:09   ` Douglas A. Gwyn
2002-06-10 10:02 ` Douglas A. Gwyn
2002-06-10 14:10 ` Blake McBride
2002-06-10 17:13   ` Quinn Dunkan
2002-06-10 18:15     ` Fariborz Tavakkolian
2002-06-10 20:43   ` FJ Ballesteros
2002-06-11  9:08   ` Don
2002-06-11  9:09   ` Douglas A. Gwyn
2002-06-12  8:54   ` Joel Salomon
2002-06-10 15:47 ` James A. Robinson
2002-06-11 15:27 ` Blake McBride
2002-06-11 17:36   ` Digby Tarvin
2002-06-11 17:44     ` James A. Robinson
2002-06-11 20:43       ` Digby Tarvin
2002-06-07  9:06 Blake McBride

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

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

  git send-email \
    --in-reply-to=20020612180513.5392819A62@mail.cse.psu.edu \
    --to=anothy@cosym.net \
    --cc=9fans@cse.psu.edu \
    /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.
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 NNTP newsgroup(s).