From: matt <matt@proweb.co.uk>
To: 9fans@cse.psu.edu
Subject: [9fans] FreeBsd & Drawterm - my weirdness
Date: Wed, 26 Mar 2003 17:20:52 +0000 [thread overview]
Message-ID: <3E81E174.3020700@proweb.co.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
I just downloaded snapshot CD and took the drawterm-freebsd from it.
When I run acme from my dump file [attached] all the glyphs are invisible.
resize acme and they appear
[-- Attachment #2.1: Type: text/plain, Size: 309 bytes --]
The following attachment had content that we can't
prove to be harmless. To avoid possible automatic
execution, we changed the content headers.
The original header was:
Content-Type: text/plain;
name="acme.dump"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="acme.dump"
[-- Attachment #2.2: acme.dump.suspect --]
[-- Type: application/octet-stream, Size: 271 bytes --]
/usr/matt
/lib/font/bit/lucidasans/unicode.13.font
/lib/font/bit/lucm/unicode.9.font
0 53
f 1 19 0 0 2
19 33 623 0 0 /usr/matt/wil0x Del Snarf | Look
reply other threads:[~2003-03-26 17:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3E81E174.3020700@proweb.co.uk \
--to=matt@proweb.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).