9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Newbie - wassup everyone?
Date: Sat, 20 Apr 2013 21:50:35 -0600	[thread overview]
Message-ID: <CAK4xykWvfri8-eoebQqBzuO3i=geX5EeNKkVty1UoRyNAFV92A@mail.gmail.com> (raw)
In-Reply-To: <84315c5350862c9cde01bc62af914c57@9srv.net>

a vote for the status quo.

keep in mind, the pastel color palette and lack of unsubtle gradient
have been chosen in rio/acme/sam/etc to keep the programmer's eyes
comfortable throughout the day. i subconsciously change all other
backgrounds and colours on my non-plan9 desktop and terminals to mimic
the plan9 ones because i find that it's the only way i can spend a day
in front of the computer and still enjoy life.

on the topic of bells and whistles: recently in my latest attempt to
"make linux work", i had to switch from unity to xfce and from xfce to
rio because i found the linux world to have moved (yet again) closer
to windows than closer to macs in terms of distractions. sure, i can't
use a few programs such as Synergy (which appears to desperately need
a tray to attach itself to), but on the other hand i don't have to
kill "pulseaudio" every time i want to listen to music. that's so 2003
it's not even funny :(

if you want an advice from the old farts on this mailing list i bet it
would be 'keep distractions to a minimum'. distracting colours too.

cheers!

ps: pastel color schemes are available now elsewhere, thankfully, and
the light "solarized" guicolor theme for vim does wonders to make it
palatable, but quite a few of those make text a pale grey. why?



  reply	other threads:[~2013-04-21  3:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21  1:44 Keith
2013-04-21  3:13 ` a
2013-04-21  3:50   ` andrey mirtchovski [this message]
2013-04-21  7:06     ` lucio
2013-04-21 12:21 Erik Quanstrom

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='CAK4xykWvfri8-eoebQqBzuO3i=geX5EeNKkVty1UoRyNAFV92A@mail.gmail.com' \
    --to=mirtchovski@gmail.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).