rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Chris Siebenmann <cks>
To: rc
Subject: Re: Beta release rc-1.6b3 available
Date: Tue, 23 Oct 2001 22:25:04 -0500	[thread overview]
Message-ID: <01Oct23.222507edt.45456@hawkwind.utcs.utoronto.ca> (raw)
In-Reply-To: schwartz's message of Mon, 22 Oct 2001 01:47:59 -0500. <20011022054759.11828.qmail@g.bio.cse.psu.edu>

| What, if anything, should we do about large file support?

 In my limited experience and experimentation, it suffixes to compile
rc with the right magic option. No actual source code changes seem

 The only seeking rc seems to do is in history.c (and that's not to
a variable position); it's otherwise pretty uncaring about most of
the large file issues. The only reason I recompiled rc with large
file support (on Linux) was so that commands could have stdin/stdout
redirected from/to large files.

 I don't know if autoconf et al has a test for large file support. If it
does, it might be worth building rc that way automatically. If not, it's
pretty easy to add the magic #define (actually usually a -D) by hand.

	- cks

  reply	other threads:[~2001-10-24  3:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 13:56 Tim Goodwin
2001-10-17 14:13 ` Buggs
2001-10-17 14:34   ` Tim Goodwin
2001-10-17 21:13     ` Buggs
     [not found] ` <20011019004843.A429@gc.wirefire.com>
2001-10-19 17:14   ` Tim Goodwin
2001-10-22  6:47     ` Scott Schwartz
2001-10-24  3:25       ` Chris Siebenmann [this message]
2001-10-24  3:41         ` Scott Schwartz
2001-10-23  7:55 ` Carlo Strozzi
2001-10-23 12:44   ` Tim Goodwin
2001-10-23 21:32     ` Carlo Strozzi
2001-10-24  3:34       ` Chris Siebenmann
2001-10-24  8:04         ` Carlo Strozzi
2001-10-23 15:47   ` Markus Friedl
2001-10-23 21:09     ` Carlo Strozzi
2001-10-23 15:55   ` Sam Roberts
2001-10-23 21:14     ` Scott Schwartz
2001-10-26 23:57 Gary Carvell

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=01Oct23.222507edt.45456@hawkwind.utcs.utoronto.ca \
    --to=rc@hawkwind.utcs.toronto.edu \


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