From: Greg A. Woods woods@most.weird.com
Subject: acme font
Date: Fri, 6 Oct 1995 12:30:19 -0400 [thread overview]
Message-ID: <19951006163019.k03KSiWXDe7gK725ppTbGqf_3Rg26Es_UKjGfUOTG38@z> (raw)
[ On Thu, October 5, 1995 at 23:40:38 (GMT), Mikael Cardell wrote: ]
> Subject: Re: acme font
>
> A simple, short example on this is this section, ripped from
> /sys/include/libg.h:
>
> /*
> * Codes for bitblt etc.
> *
> * D
> * 0 1
> * ---------
> * 0 | 1 | 2 |
> * S |---|---|
> * 1 | 4 | 8 |
> * ---------
> *
> * Usually used as D|S; DorS is so tracebacks are readable.
> */
>
> I hope you're reading this with a proportional font now. This is
> simple enough to be understood even *with* a proportional font,
> but I find a lot of examples in other's code that heavily relies on
> the use of space characters for indentation in both code and
> comments.
What you've got there is a table, which is what 'tab' characters *could*
be used for, assuming we had some way to embed the tabular
specifications inband with the text. Perhaps this could be a use for
some of the as yet un-allocated characters in Unicode?
I've been day dreaming about such things for years now! ;-)
Of course this won't help us with editing "foreign" code....
--
Greg A. Woods
+1 416 443-1734 VE3TCP robohack!woods
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
next reply other threads:[~1995-10-06 16:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-06 16:30 Greg [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-10-13 13:46 Castor
1995-10-12 7:58 Felix
1995-10-12 2:31 rob
1995-10-11 15:02 dhog
1995-10-11 4:13 Andrew
1995-10-07 21:58 Berry
1995-10-07 20:49 Scott
1995-10-07 19:37 Felix
1995-10-06 7:40 Mikael
1995-10-06 0:11 rob
1995-10-05 14:19 howard
1995-10-05 13:04 Mikael
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=19951006163019.k03KSiWXDe7gK725ppTbGqf_3Rg26Es_UKjGfUOTG38@z \
--to=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).