From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Authentication and "emu -d"
Date: Mon, 4 Jun 2001 11:06:18 +0100 [thread overview]
Message-ID: <20010604101017.9893F199D5@mail.cse.psu.edu> (raw)
>>PS: Re-reading your answer, it would seem that "emu" has two closely
>>coupled functions that could do with some decoupling, namely "dis"
>>emulation and graphics (I'm reading between the lines, I get the
>>feeling "emu -d"'s failing lies in the management of interaction with
>>its environment). Perhaps discarding the graphics baggage is an
>>option? Sounds tough to do, for little gain, but there's something to
>>be said for text-only interactions, and Plan 9 ain't going that way,
>>perhaps Inferno can.
no, not at all, that's easy to sort out.
it's the authentication that worries me.
next reply other threads:[~2001-06-04 10:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 10:06 forsyth [this message]
2001-06-04 10:36 ` Lucio De Re
-- strict thread matches above, loose matches on Subject: below --
2001-06-04 11:56 presotto
2001-06-04 9:12 forsyth
2001-06-04 9:45 ` Lucio De Re
2001-06-04 8:51 Lucio De Re
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=20010604101017.9893F199D5@mail.cse.psu.edu \
--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).