From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] p9sk2
Date: Tue, 4 Oct 2005 18:41:46 -0400 [thread overview]
Message-ID: <ee9e417a0510041541w2b567b8bx5dbe6cfe5d9f1bf5@mail.gmail.com> (raw)
In-Reply-To: <449eda812f0db45ea1ca98c567853f78@9netics.com>
> > i'm also using dt2k without any trouble (even copy/paste seems to work
> > for me just fine, in linux). i've switched to it exclusively and
> > haven't had it crash since the last recompile which happened a month
> > or two ago.
>
> i've use dt2k on windows all the time. the only problem i know of is
> the keyboard alt+char input. it isn't fatal as i can cut and paste
> out of /lib/keyboard. i think somebody already fixed this.
this has to be an issue of just not calling the latin1 code
from the windows keyboard driver. it works on linux.
russ
next prev parent reply other threads:[~2005-10-04 22:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 21:04 Uriel
2005-10-04 21:16 ` Axel Belinfante
2005-10-04 21:30 ` Axel Belinfante
2005-10-04 21:38 ` Uriel
2005-10-04 21:48 ` Skip Tavakkolian
2005-10-04 21:44 ` Russ Cox
2005-10-04 21:52 ` andrey mirtchovski
2005-10-04 22:05 ` geoff
2005-10-04 22:28 ` andrey mirtchovski
2005-10-04 22:38 ` Skip Tavakkolian
2005-10-04 22:41 ` Russ Cox [this message]
2005-10-04 22:42 ` andrey mirtchovski
2005-10-04 22:10 ` Uriel
2005-10-04 23:21 ` Skip Tavakkolian
2005-10-04 23:26 ` Russ Cox
2005-10-04 23:35 ` Russ Cox
2005-10-05 0:11 ` Uriel
2005-10-05 0:19 ` Russ Cox
2005-10-05 0:22 ` Skip Tavakkolian
2005-10-05 1:27 ` Uriel
2005-10-05 1:50 ` Russ Cox
2005-10-05 2:13 ` jmk
2005-10-05 4:56 ` LiteStar numnums
2005-10-24 13:52 ` Uriel
2005-10-24 14:17 ` jmk
[not found] ` <000001c5c94e$82d49890$14aaa8c0@utelsystems.local>
2005-10-05 5:36 ` Nils O. Selåsdal
2005-10-04 23:36 ` David Leimbach
2005-10-05 7:20 ` Richard Miller
2005-10-05 7:44 ` Skip Tavakkolian
[not found] ` <67a09890a59797f569b0456bb3edcc86@hamnavoe.com>
2005-10-05 10:46 ` 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=ee9e417a0510041541w2b567b8bx5dbe6cfe5d9f1bf5@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).