9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] color of window border
Date: Tue, 30 Sep 2003 19:57:32 -0600	[thread overview]
Message-ID: <97bca9a7ee8ffaa6861f51703c185b96@plan9.ucalgary.ca> (raw)
In-Reply-To: <87k77pu9gt.fsf@rgristroph-austin.ath.cx>


> You mean the pain and torment of flipping back to the console to type
> "startx -- :2" and test X without losing your current window state, as
> compared to the ease and simplicity of doing right button down, select
> new, sweep open new window, and typing "rio" ?
>
> --Rob

it's more like this (because i've done it):

	- finding what to edit in X's source 	-- 1 hour (500mb source!)

	- editing a small change 			-- 5 minutes

repeat:
	- rethinking whether you did the right thing while it compiles
	-- 5 minutes

	- waiting for the rest of the compile to finish
								-- 1 hour (varies)

	- goto repeat unless you're happy 	-- 0 minutes

	- pressing ctlr+alt+Fx 			-- 0 minutes

	- pressing ctlr+alt+Fx a few more times because you can't find
	where your last session where 		-- 0 minutes

	- cursing and typing your username at the login: window
								-- 1 minute

	- typing startx :2 to start new X 	-- 1 minute (and waiting for it to start)

	- finding the consequences of your change
								-- 5 minutes

	- killing X because you realized you started the wrong binary
								-- 0 minutes

	- typing $home/src/somewhere/blah/startx
								-- 5 minutes (includes making
								sure it didn't _still_ start the wrong binary)


Frustration: endless...

I'm sorry, you can't beat the functionality you get for something as
simple as Rio.  And as a developer you really can't beat the ~7000 (!)
lines of code that it comprises.

ok, there are differences (vga drivers are in the kernel, for
example).  still it's much simpler and even complete idiots like me
can understand it.  somewhat.

inflamatory subject though, i admit :)




  parent reply	other threads:[~2003-10-01  1:57 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30 16:52 Richard C Bilson
2003-09-30 16:33 ` Sam
2003-09-30 17:59 ` boyd, rounin
2003-09-30 18:49   ` C H Forsyth
2003-09-30 20:34     ` ron minnich
2003-09-30 23:45       ` Rob Ristroph
2003-10-01  0:24         ` Charles Forsyth
2003-10-01  0:50         ` matt
2003-09-30 23:37           ` boyd, rounin
2003-10-01  1:57         ` mirtchov [this message]
2003-10-01  2:02           ` ron minnich
2003-10-01  0:40       ` Charles Forsyth
2003-10-01  1:00         ` Christopher Nielsen
2003-10-01  5:32         ` Dan Cross
2003-09-30 20:36   ` Wes Kussmaul
2003-09-30 20:32     ` boyd, rounin
2003-09-30 20:58     ` mirtchov
  -- strict thread matches above, loose matches on Subject: below --
2003-09-30 18:00 Richard C Bilson
2003-09-30 15:10 a.b
2003-09-30 13:58 a.b
2003-09-30 13:59 ` Lucio De Re
2003-09-30 14:08 ` rog
2003-09-30 15:09   ` Christian Grothaus
2003-09-30 15:13     ` Fco.J.Ballesteros
2003-09-30 15:16     ` Russ Cox
2003-09-30 15:27       ` Christian Grothaus
2003-09-30 15:30     ` mirtchov
2003-09-30 15:38     ` Rob Pike
2003-09-30 16:59       ` Christian Grothaus
2003-09-30 14:19 ` ron minnich
2003-09-30 13:36 a.b
2003-09-30 13:51 ` rog
2003-09-30 14:03   ` mirtchov
2003-09-30 14:20     ` ron minnich
2003-09-30 14:24       ` Sam
2003-09-30 16:11         ` Joel Salomon
2003-09-30 16:33         ` matt
2003-10-01  4:04           ` splite
2003-10-01 10:16             ` matt
2003-10-01 10:06               ` boyd, rounin
2003-09-30 14:59       ` andrey mirtchovski
2003-09-30 15:13         ` C H Forsyth
2003-09-30 15:20           ` ron minnich
2003-09-30 15:39             ` C H Forsyth
2003-09-30 13:51 ` Christian Grothaus
2003-09-30 17:36   ` boyd, rounin

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=97bca9a7ee8ffaa6861f51703c185b96@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).