9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Jack Johnson" <knapjack@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: [9fans] 9pm customization
Date: Sat, 18 Mar 2006 06:54:14 -0800	[thread overview]
Message-ID: <6e35c0620603180654s4fa46217t4c0c0779e67f0775@mail.gmail.com> (raw)

On 3/16/06, Jack Johnson <knapjack@gmail.com> wrote:
> Speaking of which, do my eyes deceive me or did 9pm get updated on
> Halloween?  How did I miss that?
>
> Anyone know what might have changed?

As I updated the version of 9pm on my USB key (I think), I remembered
that there were bits "missing" that always drove me nuts, but I
couldn't remember which ones, so I fired up a 9term and tried some
things out.

On my work workstation I have bzip2 in the path, so I copied that
over.  Thought some more, and Inferno ships with awk, so that's there
now, too.  Both of these spit out carriage returns at the end of the
line, but they're functional and keep my fingers doing what they
should.  I pack around Inferno on the same USB key, but usually I want
to monkey with files on the host in some semi-sane fashion and it's
faster to just fire up 9pm than to jump through the hoops in Inferno.

It occurred to me that it would be handy to either recompile awk and
bzip2 to not generate the carriage return, or maybe to handle it some
other way in 9pm so all of the local Windows utilities wouldn't be
such a pain.

Getting to the point, for those of you who still use 9pm, what have
you added to your path to make it more livable?  Have you found that
any of the utilities that ship with Inferno are more up to date?

-Jack


             reply	other threads:[~2006-03-18 14:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 14:54 Jack Johnson [this message]
2006-03-19 19:05 ` Richard Bilson
2006-03-19 21:15 ` Victor Nazarov

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=6e35c0620603180654s4fa46217t4c0c0779e67f0775@mail.gmail.com \
    --to=knapjack@gmail.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).