9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Harri Haataja <realblades@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] The correct way to do an incorrect thing
Date: Thu, 29 Sep 2016 10:54:18 +0300	[thread overview]
Message-ID: <CAD8V-zDucVk4rJR6zmFVGhvFs96cYzA_=XOQg+hQBmRWjfXYzg@mail.gmail.com> (raw)
In-Reply-To: <CAFSF3XNP3FpjJ526iiPAo8Lzc3JuM2udSK6MDNfcjiV=J-5b4A@mail.gmail.com>

I thought it would be to make an XML file describing red and yellow
polkadot that is compiled in to the source because research says
that is the the background that most increases productivity.

If anyone wants to change it they're free to go edit the code and rebuild.

On 29 September 2016 at 10:48, hiro <23hiro@gmail.com> wrote:
>  no, the plan 9 way is to apply for a grant first, that would support
> such endeavor
>
> On 9/29/16, Erik Quanstrom <quanstro@quanstro.net> wrote:
>> a plan 9 thing would be to use /usr/$user/lib/acmebg and call it a day.
>>
>>
>> On Sep 28, 2016 4:07 PM, Marshall Conover <marzhall.o@gmail.com> wrote:
>>>
>>> As an awful person, I hacked rio's data.c to support backgrounds. Because
>>> the default code took a 1-by-1 pixel grey image and tiled it, I just
>>> shoved a line in there to load an image file instead using readimage().
>>> (Hacked really is the appropriate word here.)
>>>
>>> My question is, would the plan9 approach to this (assuming this were a
>>> plan 9 thing to do in the first place) be to add a command line argument
>>> to rio that lets the user specify a file, or would it be to present some
>>> file somewhere the user can write a background to? E.g., `cat
>>> /usr/glenda/backgrounds/bg.bit > /rio/bg`.
>>>
>>> If there are any papers or man pages that'd be good to read for this
>>> question, I'd appreciate a finger in that direction.

--
I appear to be temporarily using gmail's horrible interface. I
apologise for any failure in my part in trying to make it do the right
thing with post formatting.



      reply	other threads:[~2016-09-29  7:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 23:07 Marshall Conover
2016-09-28 23:58 ` Erik Quanstrom
2016-09-29  7:48   ` hiro
2016-09-29  7:54     ` Harri Haataja [this message]

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='CAD8V-zDucVk4rJR6zmFVGhvFs96cYzA_=XOQg+hQBmRWjfXYzg@mail.gmail.com' \
    --to=realblades@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).