From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Acme without Flamage
Date: Thu, 21 Aug 2008 06:35:30 -0700 [thread overview]
Message-ID: <3e1162e60808210635l1440df7bo176f80c5e315b1ae@mail.gmail.com> (raw)
In-Reply-To: <87pro3mnvl.fsf@plap.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]
On Thu, Aug 21, 2008 at 2:06 AM, Paul Donnelly
<paul-donnelly@sbcglobal.net>wrote:
> paurea@gmail.com (Gorka Guardiola) writes:
>
> > On Wed, Aug 20, 2008 at 7:42 PM, David Leimbach <leimy2k@gmail.com>
> wrote:
> >>
> >>
> >> The only thing I'd miss in Acme vs emacs then, most likely, for
> lisp-like
> >> languages is paren-matching.
> >> And I'd miss it dearly.
> >>
> >>
> >
> > Double click on the paren selects the area enclosed by the matching
> paren.
> >
> >
> >
> > --
> > - curiosity sKilled the cat
>
> I don't know if posts to usenet (where I lurk this list) go through to
> the mailing list, but I've found Acme's paren matching to be
> sufficient. The bear is indentation, since to make it work out it's
> necessary to use a fixed-width font (something I'd rather not do) and
> adjust it by hand, which needs to happen more often and by greater
> degrees than in a language like C. The chief issues being:
>
> (list (list 'a 'b 'c)
> (list 1 2 3))
> ; ^
> ; These need to line up.
>
> ; These need to line up.
> ; V
> (let ((a 3)
> (b 4))
> (+ a b))
> ; ^
> ; Should be two spaces or so.
>
>
Yeah I guess I'm spoiled by the hotkey visual cues I get from Emacs when
typing in code, that automatically show me the matching parens as I type.
Perhaps I really don't *need* that. I'll try Plan 9 Port acme again for
some Scheme Shell or something and see how it goes. (Emacs screws up Scheme
Shell pretty badly, due to it's not accepting | characters in it's syntax
definition, and as I said before, customizing emacs is not the same as me
getting my work done)
Dave
[-- Attachment #2: Type: text/html, Size: 2371 bytes --]
next prev parent reply other threads:[~2008-08-21 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 15:12 Wendell xe
2008-08-20 15:38 ` Tom Lieber
2008-08-20 15:47 ` Robert Raschke
2008-08-20 17:14 ` sqweek
2008-08-20 17:42 ` David Leimbach
2008-08-20 19:23 ` Gorka Guardiola
2008-08-21 9:06 ` Paul Donnelly
2008-08-21 13:35 ` David Leimbach [this message]
2008-08-22 4:57 ` sqweek
2008-08-22 8:38 ` 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=3e1162e60808210635l1440df7bo176f80c5e315b1ae@mail.gmail.com \
--to=leimy2k@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).