9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: <cej@gli.cas.cz>
To: <9fans@cse.psu.edu>
Subject: RE: [9fans] Plan9 for a newbie
Date: Fri,  9 Mar 2007 09:20:02 +0100	[thread overview]
Message-ID: <ACCF003CBA3D09458207DB0CB86AD17D481B37@XMAIL.asuch.cas.cz> (raw)
In-Reply-To: <56a297000703082325i66f581b4q15ca9f379b1ca5f8@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

I hope I will NEVER see icons, gradients and rounded edges on Plan9: the day
they will appear within /n/sources will be the funeral day of Plan9 on my box -- i'm NOT joking. Let this crap to other OSes, and let's continue being "OS Ferrari", as labelled earlier by someone else (can't recall who). Plan9 should not try to be for everybody, for it is the safest way to HELL.
Just IMHO, as usually. Morover, if I was able to master the basics of using Plan9
, then everyone can. Remember, I'm not a computer man, I'm a biologist. Vevertheless, I like Plan9 design, enjoy using it on an everyday basis, I got rid of Windoze long time ago and maintaining a small Linux partition just for running a web browser  with all that crap stuff like javascript etcetc... pesting most of what in past days have been HTML 1.0 webpages.
When I'm able to install abaco and configure acme mail, i'll get rid of linux, too.

Best regards,
++pac.


-----Original Message-----
From: 9fans-bounces+cej=gli.cas.cz@cse.psu.edu on behalf of Noah Evans
Sent: Fri 3/9/2007 8:25 AM
To: Fans of the OS Plan 9 from Bell Labs
Subject: Re: [9fans] Plan9 for a newbie
 
I think what Plan 9 really needs is a screencast. If people could
actually *see* what it was like to use p9 they'd come running. Most
users coming from linux seem to get frustrated and move on quickly.

All you'd need to do then is add some gradients and rounded edges to
rio and acme.

Noah

On 3/9/07, Jack Johnson <knapjack@gmail.com> wrote:
> On 3/8/07, ron minnich <rminnich@gmail.com> wrote:
> > The list is pretty endless.
>
> Nice job, Ron!
>
> This should be in Glenda's default inbox.
>
> -Jack
>


[-- Attachment #2.1: Type: text/plain, Size: 292 bytes --]

from postmaster@ethel:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/ms-tnef;
	name="winmail.dat"
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: winmail.dat.suspect --]
[-- Type: application/octet-stream, Size: 3763 bytes --]

  reply	other threads:[~2007-03-09  8:20 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 20:32 Jim Ford
2007-03-08 20:46 ` erik quanstrom
2007-03-08 20:56 ` Gabriel Díaz
2007-03-08 21:00   ` andrey mirtchovski
2007-03-08 21:02 ` Federico G. Benavento
2007-03-08 21:40 ` ron minnich
2007-03-08 21:49   ` erik quanstrom
2007-03-08 22:02   ` Federico G. Benavento
2007-03-09  1:01     ` Joel Franusic
2007-03-09  3:21   ` Jack Johnson
2007-03-09  7:25     ` Noah Evans
2007-03-09  8:20       ` cej [this message]
2007-03-09 15:56   ` John Floren
2007-03-09  6:58 ` Markus Sonderegger
2007-03-09  9:12   ` Kris Maglione
2007-03-09 13:43     ` erik quanstrom
2007-03-09 10:15   ` Charles Forsyth
2007-03-09 15:47     ` David Leimbach
2007-03-09 17:20       ` C H Forsyth
2007-03-09 19:12       ` Federico Benavento
2007-03-09 10:33 ` John Stalker

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=ACCF003CBA3D09458207DB0CB86AD17D481B37@XMAIL.asuch.cas.cz \
    --to=cej@gli.cas.cz \
    --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).