rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@speakeasy.net>
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: Release candidate rc-1.6c4 available
Date: Thu, 1 Nov 2001 11:20:00 -0500	[thread overview]
Message-ID: <20011101162000.072423F403@quanstro.net> (raw)

okay, i'm missing something. what was needed to have
rc support large files? there is only one seek in
rc -- and it seeks 0 bytes from the end of the history
file. that can't be it. a grep for _LARGE_FILES doesn't
reveal anything either.

so where's the change?



A new beta release, which is also a release candidate for the next
full release, is available from the usual place.


I've appended the (short!) ChangeLog since the last beta release.

I need your help to decide if this release candidate is a trick or a
treat.  I'm using this version (with GNU readline) on RedHat, SunOS,
and Tru64.  I've also built and tripped it on CygWin, Irix, NetBSD,
and OpenBSD.  *Particularly* if you're using a different OS than
these, I need you to test out this release candidate, and let me know
how it goes.  But if you're using one of these, you're not excused:
test it anyway, try a different line editing library, proof read some

As always, your feedback makes rc better for everyone.




  Feature: large file support (thanks Scott Schwartz, Chris


  Bug: space vs tab confusion in commented out Makefile rules to
  rebuild parser (thanks Gary Carvell).


  Documentation: subscripted variables don't work in here documents.

  Release: rc-1.6c4.

             reply	other threads:[~2001-11-01 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 16:20 erik quanstrom [this message]
2001-11-01 17:46 ` Scott Schwartz
  -- strict thread matches above, loose matches on Subject: below --
2001-10-31 16:18 Tim Goodwin
2001-11-01 17:35 ` Stefan Dalibor
2001-11-04 17:58 ` Scott Kenney

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011101162000.072423F403@quanstro.net \
    --to=quanstro@speakeasy.net \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --subject='Re: Release candidate rc-1.6c4 available' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).