From: Russ Cox <rsc@swtch.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] drawterm
Date: Fri, 4 Nov 2005 12:21:27 -0500 [thread overview]
Message-ID: <ee9e417a0511040921r573aed59laef8b2aece90b86b@mail.gmail.com> (raw)
I am almost ready to declare dt2k "stable".
The random lock-ups were due to suspect X11 use
that I cleaned up a few weeks ago.
The fcp bug I mentioned before turns out to be a
problem with Plan 9, not with drawterm. The bug was
in devssl (or in devmnt, depending on how you look at it),
not in drawterm. There is a new /sys/src/9/port/devssl.c
and devmnt.c on sources.
There are new drawterm binaries at http://swtch.com/drawterm/
If you build yourself a kernel with the new devssl/devmnt
and are running the latest drawterm and see it crash or
do something else wrong, please let me know.
The latest drawterm has one new feature: if you are running
a plan9port factotum, then drawterm will use it.
Russ
next reply other threads:[~2005-11-04 17:21 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 17:21 Russ Cox [this message]
2005-11-04 20:09 ` Gabriel Diaz
2005-11-04 18:21 ` "Nils O. Selåsdal"
2005-11-04 20:47 ` Gabriel Diaz
2005-11-04 20:18 ` Russ Cox
2005-11-04 20:13 ` Axel Belinfante
2005-11-04 22:14 ` Axel Belinfante
2005-11-04 22:43 ` Axel Belinfante
2005-11-05 21:46 ` [9fans] drawterm on solaris Axel Belinfante
2005-11-05 21:55 ` Axel Belinfante
2005-11-05 23:09 ` Axel Belinfante
2005-11-04 22:50 ` [9fans] drawterm Brantley Coile
2005-11-04 23:01 ` andrey mirtchovski
2005-11-04 23:04 ` Brantley Coile
2005-11-04 23:08 ` Tim Wiess
2005-11-04 23:16 ` andrey mirtchovski
2005-11-07 17:49 ` [9fans] drawterm Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 19:28 [9fans] drawterm Steve Simon
2005-10-18 14:00 Russ Cox
2005-10-06 8:22 Andrew Simmons
2005-10-06 9:47 ` Dave Lukes
2005-10-06 14:25 ` Vester Thacker
2005-10-06 13:16 ` Brantley Coile
2005-10-06 15:08 ` Russ Cox
2005-10-05 12:12 Russ Cox
2004-08-12 20:26 boyd, rounin
2004-08-12 23:47 ` Russ Cox
2004-08-13 0:03 ` boyd, rounin
2003-12-17 13:51 boyd, rounin
2003-12-17 4:10 ` okamoto
2003-12-17 14:31 ` boyd, rounin
2003-12-17 7:11 ` Dan Cross
2003-09-10 14:38 David Presotto
2003-09-10 14:48 ` mirtchov
2003-09-10 16:00 ` andrey mirtchovski
2003-09-10 19:47 ` Atanas Bachvaroff
2003-09-10 21:00 ` Geoff Collyer
2003-09-11 6:18 ` okamoto
2003-09-11 13:12 ` mirtchov
2003-09-12 1:07 ` okamoto
2003-09-11 14:17 ` Axel Belinfante
2003-09-12 2:10 ` okamoto
2003-09-11 2:05 ` boyd, rounin
2003-09-11 4:31 ` Skip Tavakkolian
2002-07-17 22:18 rob pike, esq.
2002-07-17 21:17 Sam
2002-07-17 21:25 ` Sam
2000-12-20 4:11 Russ Cox
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=ee9e417a0511040921r573aed59laef8b2aece90b86b@mail.gmail.com \
--to=rsc@swtch.com \
--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).