9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] gs
Date: Tue,  3 Oct 2006 22:41:38 +0200	[thread overview]
Message-ID: <8ccc8ba40610031341h4f6bd9a6y34fa0c9142b5b0c5@mail.gmail.com> (raw)
In-Reply-To: <c149e38182585738606b03e2e27a478e@terzarima.net>

I'm curious. any other interpreter that could be ported?

On 10/3/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> as tedious as waiting for gs to do something is waiting
> for db to load all its symbols to debug it not doing something.
> if they ever find another candidate for a planet to replace pluto,
> they should call it `ghostscript'.  it will be big enough to qualify.
>
> out of idle interest, why has there never been a replacement?
> is it really that hard?
>
>
>


  parent reply	other threads:[~2006-10-03 20:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-03 13:10 [9fans] OT: scsi sense error code hardware error 40 83? Axel Belinfante
2006-10-03 18:17 ` geoff
2006-10-03 20:13   ` [9fans] kenfs config? (was: OT: scsi sense error code hardware error 40 83?) Axel Belinfante
2006-10-03 21:19     ` [9fans] kenfs config? (was: OT: scsi sense error code hardware geoff
2006-10-17 15:55       ` Axel Belinfante
2006-10-17 20:18         ` geoff
2006-10-17 21:05           ` Axel Belinfante
2006-10-17 21:35             ` geoff
2006-10-17 23:55               ` Axel Belinfante
2006-10-03 20:20   ` [9fans] gs Charles Forsyth
2006-10-03 20:39     ` geoff
2006-10-03 20:41     ` Francisco J Ballesteros [this message]
2006-10-03 20:48     ` Jack Johnson
2006-10-03 21:37       ` LiteStar numnums
2006-10-03 22:07         ` Andy Newman
2006-10-04  2:18       ` jmk
2006-10-06  0:00         ` Bruce Ellis
2007-08-21 23:07 Steve Simon

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=8ccc8ba40610031341h4f6bd9a6y34fa0c9142b5b0c5@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).