From: Daniel Lyons <fusion@storytotell.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Using proportional fonts in Acme for Programming
Date: Thu, 13 Aug 2009 11:55:33 -0600 [thread overview]
Message-ID: <680C3DA2-9DBC-4524-8F6E-31885F9E7446@storytotell.org> (raw)
In-Reply-To: <op.uyka0s1y0p3ku8@localhost>
On Aug 13, 2009, at 3:14 AM, Aaron W. Hsu wrote:
> So, I was browsing around the other day looking at Acme resources,
> and I discovered an old post from 1995 wherein someone advocated the
> use of proportional fonts for programming in Acme. This surprised
> me, to say the least. He even went as far as to mention that SML was
> the language they were using, and had managed to get a decent
> indenting pattern for it that was just as readable, without messing
> things up for proportional font users.
>
> I have to admit that I'm a bit skeptical about whether such a
> technique actually works, and so, I thought I would pose some
> questions to you.
Bjarne Stroustrup actually advocates this style in "The C++
Programming Language."
This discussion reminds me of this elastic tab stops concept:
http://nickgravgaard.com/elastictabstops/
I don't think it made it into any editors, but it would support the
kind of fancy alignment I like to have in my code while also
supporting real fonts, which I would prefer to use.
> Thirdly, would you continue using proportional width fonts in cases
> like Lisp code, where you very often see something like the
> following indentation scheme, and how would you resolve these
> indentation problems with proportional width fonts if you did
> continue to use them?
>
> (let ([foo bar]
> [something else])
> (some-func (called again)
> (with fun indentation)
> (and yet)
> (another)))
I bet you could set up Emacs to use a proportional font. It can do
anything, right? :)
I'd love it if Acme or Plan 9 had good support for some kind of Lisp
variant.
—
Daniel Lyons
next prev parent reply other threads:[~2009-08-13 17:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 9:14 Aaron W. Hsu
2009-08-13 10:09 ` matt
2009-08-13 10:18 ` Paul Donnelly
2009-08-13 10:22 ` roger peppe
2009-08-13 10:27 ` Robert Raschke
2009-08-13 11:12 ` Ethan Grammatikidis
2009-08-13 17:55 ` Daniel Lyons [this message]
2009-08-13 22:27 ` David Leimbach
2009-08-13 22:35 ` ron minnich
2009-08-13 22:40 ` erik quanstrom
2009-08-14 2:58 ` Roman V. Shaposhnik
2009-08-14 8:27 ` Robert Raschke
2009-08-14 18:27 ` [9fans] Lua on Plan9 Roman V. Shaposhnik
2009-08-14 21:47 ` John Floren
2009-08-14 21:52 ` Josh Wood
2009-08-14 21:54 ` John Floren
2009-08-17 10:34 ` Robert Raschke
2009-08-14 21:32 ` [9fans] Using proportional fonts in Acme for Programming Skip Tavakkolian
2009-08-14 9:16 ` Pavel Klinkovsky
2009-08-14 18:25 ` [9fans] Lua on Plan9 Roman V. Shaposhnik
2009-08-14 21:48 ` Skip Tavakkolian
2009-08-14 23:26 ` [9fans] Using proportional fonts in Acme for Programming Noah Evans
2009-08-15 2:28 ` Akshat Kumar
2009-08-15 10:29 ` Akshat Kumar
2009-08-17 9:09 ` Aaron W. Hsu
2009-08-17 9:09 ` Aaron W. Hsu
2009-08-14 9:15 ` Aaron W. Hsu
2009-08-14 16:49 ` Daniel Lyons
2009-08-14 18:28 ` Roman V. Shaposhnik
2009-08-16 7:30 ` Daniel Lyons
2009-08-17 9:09 ` Aaron W. Hsu
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=680C3DA2-9DBC-4524-8F6E-31885F9E7446@storytotell.org \
--to=fusion@storytotell.org \
--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).