From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Small program "PlanKey" (paraphrase of DOSKey)
Date: Tue, 27 Jan 2009 14:50:48 -0800 [thread overview]
Message-ID: <1233096648.22808.334.camel@goose.sun.com> (raw)
In-Reply-To: <e0ac85f90901271443y37e9e2a2g63b972a50c75294@mail.gmail.com>
On Tue, 2009-01-27 at 14:43 -0800, Christopher Nielsen wrote:
> On Tue, Jan 27, 2009 at 14:31, Roman V. Shaposhnik <rvs@sun.com> wrote:
> > On Tue, 2009-01-27 at 14:25 -0800, Christopher Nielsen wrote:
> >> > ... I've seen this study and I tend to believe it. But there's a gotcha:
> >> > the kind of work that I and other software engineers do with computers
> >> > is almost orthogonal to what the study was focusing on. I don't believe
> >> > anybody else, but engineers, spend the majority of time dealing with
> >> > text.
> >>
> >> Who do you think Plan 9 was designed for and by?
> >
> > For researches by researches. You have a different explanation?
>
> By programmers for programmers.
Are you a programmer? Care to give pointers to the projects you've
been on?
> No need to reply. This is my last post on the subject.
I get it! You are not a programmer -- you are a phone prankster.
Thanks,
Roman.
next prev parent reply other threads:[~2009-01-27 22:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 10:03 pavel.klinkovsky
2009-01-23 10:50 ` Francisco J Ballesteros
2009-01-23 11:27 ` Pietro Gagliardi
2009-01-23 11:35 ` Pietro Gagliardi
2009-01-23 12:56 ` roger peppe
2009-01-23 14:14 ` erik quanstrom
2009-01-26 12:41 ` cej
2009-01-26 10:31 ` pavel.klinkovsky
2009-01-27 3:29 ` Roman Shaposhnik
2009-01-27 3:42 ` erik quanstrom
2009-01-27 4:43 ` Roman Shaposhnik
2009-01-27 6:35 ` Akshat Kumar
2009-01-27 6:44 ` Akshat Kumar
2009-01-27 20:01 ` Roman V. Shaposhnik
2009-01-27 20:10 ` erik quanstrom
2009-01-27 22:01 ` Roman V. Shaposhnik
2009-01-27 22:26 ` erik quanstrom
2009-01-27 22:58 ` sqweek
2009-01-27 23:42 ` erik quanstrom
2009-01-28 0:35 ` Anthony Sorace
2009-01-28 5:59 ` lucio
2009-01-28 19:00 ` erik quanstrom
2009-01-28 22:19 ` Joel C. Salomon
2009-01-28 22:51 ` Francisco J Ballesteros
2009-01-29 0:26 ` Akshat Kumar
2009-01-29 2:09 ` erik quanstrom
2009-01-29 8:49 ` cej
2009-01-29 11:50 ` Anthony Sorace
2009-01-29 13:04 ` roger peppe
2009-01-29 13:53 ` cej
2009-01-29 16:14 ` jimmy brisson
2009-01-29 13:53 ` erik quanstrom
2009-01-29 15:20 ` Akshat Kumar
2009-01-29 16:40 ` Roman V. Shaposhnik
2009-01-29 16:52 ` erik quanstrom
2009-01-29 17:03 ` Akshat Kumar
2009-01-29 17:09 ` Brian L. Stuart
2009-01-27 7:09 ` Russ Cox
2009-01-27 22:12 ` Roman V. Shaposhnik
2009-01-27 22:25 ` Christopher Nielsen
2009-01-27 22:31 ` Roman V. Shaposhnik
2009-01-27 22:43 ` Christopher Nielsen
2009-01-27 22:50 ` Roman V. Shaposhnik [this message]
2009-01-27 23:11 ` Christopher Nielsen
2009-01-27 23:40 ` Roman V. Shaposhnik
2009-01-28 3:15 ` Christopher Nielsen
2009-01-28 7:22 ` Eris Discordia
2009-01-27 23:01 ` sqweek
2009-01-26 10:31 ` pavel.klinkovsky
2009-01-27 3:21 ` Roman Shaposhnik
2009-01-27 9:37 ` Pavel Klinkovsky
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=1233096648.22808.334.camel@goose.sun.com \
--to=rvs@sun.com \
--cc=9fans@9fans.net \
/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).