9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Why does Acme only show text?
Date: Wed, 15 Jul 2009 14:54:37 -0500	[thread overview]
Message-ID: <d50d7d460907151254h1eb3ba0fxc37c5189c9d71e70@mail.gmail.com> (raw)
In-Reply-To: <3e1162e60907151159g5b031e99k2ad8171c9c268392@mail.gmail.com>

> Again, the layout mode seems to be a bug in Haskell not a feature, but
> that's not a popular belief in that community.

It's only as complex as the various levels of scope you end up needing
in your program.  Meaningful whitespace enforces a clean, readable,
delimiter-free style, making programs look more like each other.  It's
a lot easier to see (and not have in the first place) incorrect scope
and continuation with whitespace than with braces or parentheses.

Acme only has two indentation rules (nothing, or same as the existing
line), so Emacs' constant re-parsing of the file to determine the
correct indentation level is always going to be more "correct".  This
kind of programming support seems akin to me to colorful syntax
highlighting: great if you need it, distracting once you really get
good with a language.  In the case of indenting, I might not actually
code the next line right away, but auto-indent to just the right place
for it means I have to go out of my way more often to get the cursor
to where I actually want it.

> Dave

Jason Catena



  parent reply	other threads:[~2009-07-15 19:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15  1:58 Jason Catena
2009-07-15  4:36 ` Rob Pike
2009-07-15  5:02   ` David Leimbach
2009-07-15 13:11   ` Charles Forsyth
2009-07-16  9:58   ` cej
2009-07-16 10:41     ` mattmobile
2009-07-16 12:11     ` michael block
2009-07-16 12:29       ` cej
2009-07-15  9:25 ` Paul Donnelly
2009-07-15 12:22   ` Ethan Grammatikidis
2009-07-15 15:32     ` cej
2009-07-15 15:44       ` Ethan Grammatikidis
2009-07-15 17:00         ` John Floren
2009-07-15 18:24           ` Francisco J Ballesteros
2009-07-15 18:26           ` Steve Simon
2009-07-15 18:59             ` David Leimbach
2009-07-15 19:07               ` John Floren
2009-07-15 19:27                 ` David Leimbach
2009-07-15 20:58                 ` Chad Brown
2009-07-15 21:07                   ` John Floren
2009-07-15 19:54               ` Jason Catena [this message]
2009-07-15 19:59                 ` erik quanstrom
2009-07-15 20:05                   ` andrey mirtchovski
2009-07-15 20:14                   ` Devon H. O'Dell
2009-07-15 20:29                     ` Jason Catena
2009-07-15 20:42                       ` Noah Evans
2009-07-15 20:51                         ` David Leimbach
2009-07-15 21:27                           ` Ethan Grammatikidis
2009-07-15 23:31                             ` Jason Catena
2009-07-15 21:07                         ` Ethan Grammatikidis
2009-07-15 21:12                           ` erik quanstrom
2009-07-15 21:32                             ` Ethan Grammatikidis
2009-07-15 20:41                     ` Lyndon Nerenberg
2009-07-15 21:00     ` Federico G. Benavento
2009-07-15 21:14       ` David Leimbach
2009-07-16  8:51     ` Paul Donnelly

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=d50d7d460907151254h1eb3ba0fxc37c5189c9d71e70@mail.gmail.com \
    --to=jason.catena@gmail.com \
    --cc=9fans@9fans.net \
    /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).