9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] pico
Date: Mon,  4 Feb 2008 22:01:47 -0500	[thread overview]
Message-ID: <FE6B642F-8FF8-4766-A724-9331D5ACBF55@mac.com> (raw)
In-Reply-To: <775b8d190801302341o7bcfff79w805b5d0c82bbb7de@mail.gmail.com>

Okay, I got everything fixed a few days ago and added some more
features (simple arrays, r "long/file/name.1", etc.). The new pico is
in the usual place.

I'm redesigning my website, so I'm going to have my software
available from there too when that's done.

On Jan 31, 2008, at 2:41 AM, Bruce Ellis wrote:

> more debugging, please tell us about it.  yawn.
>
> On Jan 31, 2008 10:55 AM, Pietro Gagliardi <pietro10@mac.com> wrote:
>>
>> Well, I got the memory tampering bugs fixed, but a black and white
>> image now
>> does not show correctly. Gonna go back and check and fix. Will
>> report when I
>> put a new version up.
>>
>>
>>
>> On Jan 30, 2008, at 6:42 PM, Pietro Gagliardi wrote:
>>
>> What do you think I've been doing? :-)
>>
>> The problem seems to be in run(), because after run() returns,
>> poolcheck
>> fails. I'll go check it out.
>>
>> On Jan 30, 2008, at 1:53 AM, Bruce Ellis wrote:
>>
>> work it out.  it's called debugging.
>>
>> brucee
>>
>>


  reply	other threads:[~2008-02-05  3:01 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-25 22:05 [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-26 14:05 ` Russ Cox
2008-01-26 14:09   ` Pietro Gagliardi
2008-01-26 14:55     ` Russ Cox
2008-01-26 23:22       ` Pietro Gagliardi
2008-01-27 18:05         ` Skip Tavakkolian
2008-01-27 18:55           ` Pietro Gagliardi
2008-01-27 19:29             ` [9fans] pico Steve Simon
2008-01-28 23:36               ` Russ Cox
2008-01-29  0:30                 ` Pietro Gagliardi
2008-01-29  5:30                   ` Bruce Ellis
2008-01-29 20:33                     ` Pietro Gagliardi
2008-01-29 20:35                       ` Pietro Gagliardi
2008-01-29 22:46                         ` Russ Cox
2008-01-30  1:13                           ` Pietro Gagliardi
2008-01-30  6:53                             ` Bruce Ellis
2008-01-30 23:42                               ` Pietro Gagliardi
2008-01-30 23:55                                 ` Pietro Gagliardi
2008-01-31  7:41                                   ` Bruce Ellis
2008-02-05  3:01                                     ` Pietro Gagliardi [this message]
2008-01-27 19:14           ` [9fans] How to read/write pixels from Memimage Pietro Gagliardi
2008-01-27 23:44           ` Pietro Gagliardi
2008-01-28  0:18             ` Pietro Gagliardi
2008-01-28  1:08               ` Pietro Gagliardi
2008-01-28  1:22                 ` erik quanstrom
2008-01-28  3:23                   ` Pietro Gagliardi
2008-01-28  9:24                     ` mattmobile
2008-01-28 16:20                       ` ron minnich
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17 23:06 [9fans] pico Fariborz (Skip) Tavakkolian
2002-07-17 21:57 ` Sam

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=FE6B642F-8FF8-4766-A724-9331D5ACBF55@mac.com \
    --to=pietro10@mac.com \
    --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).