From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme fonts
Date: Wed, 15 Oct 2003 06:30:13 +0100 [thread overview]
Message-ID: <6ba0925991cdd3c073fb49b72c42d2c1@caldo.demon.co.uk> (raw)
In-Reply-To: <20031015094451.6be46dd7.ggm@apnic.net>
tabs indent code consistently for me and i use a range of typefaces
(depending where i am and what i'm using for display). if the size
set for space is relatively small, i suppose there might well be a problem.
ah. but what about
int fred;
long jim;
or
static int fred;
extern long jim;
perhaps i just write
static int fred;
extern long jim;
or i put the tabs in for old times' sake but don't fuss. the things don't line
up if you use different tab settings anyway, so what's the point. worst is
the code that uses a mixture of tabs and spaces, but that's not usual in Plan 9 source.
for me, easily the most useful thing to improve being able to read and
write C would be to eliminate that annoying need for forward
declaration of functions when compilers slurp in the whole thing.
ugh.
next prev parent reply other threads:[~2003-10-15 5:30 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 16:43 Fco.J.Ballesteros
2003-10-13 16:49 ` David Presotto
2003-10-13 16:56 ` Fco.J.Ballesteros
2003-10-13 19:02 ` vdharani
2003-10-13 19:35 ` Dan Cross
2003-10-14 8:09 ` Charles Forsyth
2003-10-14 8:13 ` Rob Pike
2003-10-14 11:17 ` David Presotto
2003-10-14 23:44 ` George Michaelson
2003-10-15 5:30 ` Charles Forsyth [this message]
2003-10-15 10:28 ` Brantley Coile
2003-10-14 19:36 ` vdharani
2003-10-15 5:40 ` Charles Forsyth
2003-10-14 0:04 ` rob pike, esq.
2003-10-15 7:29 ` Fco.J.Ballesteros
2003-10-14 12:17 David Presotto
2003-10-14 15:51 ` Rob Pike
2003-10-15 3:27 ` david presotto
2003-10-14 16:04 ` chris
2013-12-11 18:45 [9fans] Acme: fonts Blake McBride
2013-12-11 18:52 ` andrey mirtchovski
2013-12-11 19:05 ` Christopher Wilson
2013-12-11 19:12 ` Blake McBride
2013-12-11 19:15 ` erik quanstrom
2013-12-11 19:19 ` Christopher Wilson
2013-12-11 19:26 ` sl
2013-12-11 19:33 ` Rubén Berenguel
2013-12-11 19:50 ` Blake McBride
2013-12-11 19:53 ` Rubén Berenguel
2013-12-11 20:04 ` Blake McBride
2013-12-11 20:12 ` Rubén Berenguel
2013-12-11 20:26 ` Mark van Atten
2013-12-11 20:03 ` sl
2013-12-11 20:06 ` erik quanstrom
2013-12-11 20:30 ` sl
2013-12-11 20:40 ` erik quanstrom
2013-12-11 20:47 ` Mark van Atten
2013-12-11 21:04 ` sl
2013-12-11 20:15 ` Aram Hăvărneanu
2013-12-11 20:38 ` Blake McBride
2013-12-11 21:10 ` Blake McBride
2013-12-11 21:14 ` andrey mirtchovski
2013-12-11 21:21 ` Blake McBride
2013-12-11 21:25 ` Blake McBride
2013-12-11 21:25 ` Lyndon Nerenberg
2013-12-11 21:56 ` Blake McBride
2013-12-11 22:00 ` Lyndon Nerenberg
2013-12-11 22:05 ` Blake McBride
2013-12-11 22:08 ` Mark van Atten
2013-12-11 19:32 ` Oleksandr Iakovliev
[not found] <CAA8EjDRkQDO+wL1tuTQ6GMxs7rqNji4qFM80F5Kz-H0UR24R4w@mail.gmail.com>
2020-07-21 23:21 ` Acme fonts Anthony Martin
2020-07-22 18:52 ` [9fans] " Russ Cox
2020-07-22 22:47 ` Charles Forsyth
2020-07-22 23:05 ` Rob Pike
2020-07-23 3:38 ` ori
2020-07-23 4:31 ` Rob Pike
2020-07-23 5:27 ` Lucio De Re
2020-07-23 13:08 ` Ethan Gardener
2020-11-20 21:31 ` Yaroslav K
2020-11-20 22:01 ` Stuart Morrow
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=6ba0925991cdd3c073fb49b72c42d2c1@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--cc=9fans@cse.psu.edu \
/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).