From: john@csplan9.rit.edu
To: 9fans@9fans.net
Subject: [9fans] rio with virtuals
Date: Mon, 15 Jun 2009 18:54:58 -0400 [thread overview]
Message-ID: <5bb5eb6954cf188a69c95db80aff77b2@csplan9.rit.edu> (raw)
I spent a couple hours this afternoon reading rio source and hacking
it to do virtual desktops. /n/sources/contrib/john/rio-virtual.tgz
contains the files from /sys/src/cmd/rio with my changes made. At
this time, there is no support for specifying the number of virtuals,
because I'm lazy--you get six and you will ENJOY IT.
Let me know if you try it and find bugs. I don't really give a damn
if you think this is Against The Plan 9 Way. Personally, the exercise
gave me a better appreciation for the simplicity of Plan 9 software--I
was able to take a piece of software I'd never looked at before, read
the code a bit, and put in some new functionality within an hour or
two.
John
next reply other threads:[~2009-06-15 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-15 22:54 john [this message]
2009-06-15 23:00 ` J.R. Mauro
2009-06-15 23:13 ` john
2009-08-12 20:20 ` John Floren
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=5bb5eb6954cf188a69c95db80aff77b2@csplan9.rit.edu \
--to=john@csplan9.rit.edu \
--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).