From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] latin1() and unicode()?
Date: Wed, 23 May 2001 13:45:36 -0400 [thread overview]
Message-ID: <200105231745.NAA05918@augusta.math.psu.edu> (raw)
In-Reply-To: <20010523164649.D8DE119A14@mail.cse.psu.edu>
In article <20010523164649.D8DE119A14@mail.cse.psu.edu> you write:
>I'd tend toward including it manually where
>you want it until you're sure it's useful
>enough to be in the library.
Hmm... Fair enough.
>Personally I don't see it as too applicable elsewhere.
It'd be very useful for writing user-level software to
drive serial keyboards. :-) But including it out of
the kernel shouldn't be so hard.
Turning off the serial console on the bitsy; now that's
hard (or at least tedious).
- Dan C.
next prev parent reply other threads:[~2001-05-23 17:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 16:46 Russ Cox
2001-05-23 17:45 ` Dan Cross [this message]
2001-05-23 18:10 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 22:06 forsyth
2001-05-24 0:22 ` Boyd Roberts
2001-05-23 16:29 Dan Cross
2001-05-23 22:00 ` 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=200105231745.NAA05918@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).