9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mikael Cardell mkc@bull.se
Subject: acme font
Date: Fri,  6 Oct 1995 03:40:38 -0400	[thread overview]
Message-ID: <19951006074038.AJ30FxgFUFxDMwjSm5RsjJZEnQ59MmkjnpdPhmlxUDw@z> (raw)

Rob and Howard are correct in that a proportional font gives more
characters on the screen and they both advise me to stick with the
proportional font while programming and to use tab indenting to
make it look good. 

I'm perfectly fine with this advise, and I understand, and perhaps 
agree with it. However, it would be simple to follow this advise if
I was only working with my own code or code written by collegaues
that I can communicate with. As it is, I'm often working with 
code written by others, not known to me. And comments in such
code often rely on a fixed 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.

Thanks for the tip on the use of Font and B2, by the way.

Mikael Cardell <mkc@bull.se>
BOFH @ Telco Solutions, SI&S, Bull Northern Europe
(Do I look like I'm speaking for Bull?)






             reply	other threads:[~1995-10-06  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-10-06  7:40 Mikael [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 16:30 Greg
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=19951006074038.AJ30FxgFUFxDMwjSm5RsjJZEnQ59MmkjnpdPhmlxUDw@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).