From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
Date: Thu, 30 May 2002 23:01:57 +0100 [thread overview]
Message-ID: <7b6fb49ed1e84820bfde7c9c8094f09c@caldo.demon.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
>>really?
>>the only ones i could find were misc/unicode.6x13.font and
>>misc/latin1.6x1[30].font. maybe fonts have been updated for the 4th
>>edition?
you're right. it has changed. try it in the office.
> 2420 symbol for space
>is in lucida/unicode.*.font
oh i see! not having found it in the fonts i'd assumed it was the conventional symbol
for space anciently, but that little SP is not what i'd expected.
[-- Attachment #2: Type: message/rfc822, Size: 1615 bytes --]
To: 9fans@cse.psu.edu
Subject: Re: [9fans] spaces in file/dir names? (and acme)?
Date: Thu, 30 May 2002 21:16:03 +0100
Message-ID: <20020530201120.CFF9A19AB0@mail.cse.psu.edu>
> i tend to use no-break space (00a0) which has dots in two corners in
> the usual plan 9 fonts, although
really?
the only ones i could find were misc/unicode.6x13.font and
misc/latin1.6x1[30].font. maybe fonts have been updated for the 4th
edition?
> 2420 symbol for space
is in lucida/unicode.*.font
next reply other threads:[~2002-05-30 22:01 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-30 22:01 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 10:29 Fco.J.Ballesteros
2002-06-06 10:48 ` Axel Belinfante
2002-06-06 8:11 Fco.J.Ballesteros
2002-06-06 10:22 ` Axel Belinfante
2002-06-05 18:39 Geoff Collyer
2002-06-05 17:55 rog
2002-06-05 17:04 anothy
2002-06-05 13:46 Russ Cox
2002-06-03 7:48 Fco.J.Ballesteros
2002-06-03 16:05 ` Dan Cross
2002-06-05 10:05 ` Douglas A. Gwyn
2002-06-01 21:37 jmk
2002-06-01 22:06 ` Dan Cross
2002-05-30 20:16 rog
2002-05-30 20:14 rsc
2002-05-30 19:29 rog
2002-05-30 19:12 forsyth
2002-05-30 18:58 rog
2002-05-30 18:55 rsc
2002-05-30 18:16 rog
2002-06-04 16:23 ` Axel Belinfante
2002-05-30 18:15 rsc
2002-05-30 18:13 Geoff Collyer
2002-05-31 4:53 ` Lucio De Re
2002-05-31 8:59 ` Boyd Roberts
2002-05-30 18:09 Sape Mullender
2002-05-30 17:58 Fco.J.Ballesteros
2002-05-30 17:10 ` Sam
2002-05-30 17:52 presotto
2002-05-30 17:46 Geoff Collyer
2002-05-30 17:00 Fco.J.Ballesteros
2002-06-01 21:34 ` Dan Cross
2002-05-30 16:57 Fco.J.Ballesteros
2002-05-30 17:03 ` Lucio De Re
2002-06-05 9:55 ` Douglas A. Gwyn
2002-05-30 16:30 rsc
2002-05-30 16:35 ` Axel Belinfante
2002-06-05 9:54 ` Douglas A. Gwyn
2002-05-30 16:30 rsc
2002-05-30 16:21 Axel Belinfante
2002-05-30 16:27 ` Boyd Roberts
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=7b6fb49ed1e84820bfde7c9c8094f09c@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).