From scsh-users-request@scsh.net Tue Feb 14 17:34:43 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 2B1A5115; Tue, 14 Feb 2006 17:34:42 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43272-03; Tue, 14 Feb 2006 17:34:39 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 9FC87112; Tue, 14 Feb 2006 17:34:37 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 95B7B5ED2; Tue, 14 Feb 2006 17:34:36 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net X-Injected-Via-Gmane: http://gmane.org/ To: scsh-users@scsh.net From: Wolfgang Hukriede Subject: how do I write "(a; b) >file" in scsh? Date: Tue, 14 Feb 2006 15:38:00 +0000 (UTC) Lines: 9 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: main.gmane.org User-Agent: Loom/3.14 (http://gmane.org/) X-Loom-IP: 82.97.175.40 (Opera/8.51 (X11; FreeBSD i386; U; en)) Sender: news Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/247 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Tue, 14 Feb 2006 17:34:36 +0100 (MET) Here's a very simply question: how do I write "(a; b) >file" in scsh? I came up with (run (begin (run (a)) (run (b))) (> file)) but this looks a bit ridiculous, right? Many thanks! From scsh-users-request@scsh.net Wed Feb 15 00:14:42 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 95F0E13D; Wed, 15 Feb 2006 00:14:40 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 38242-01; Wed, 15 Feb 2006 00:14:33 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8CF9B101; Wed, 15 Feb 2006 00:14:28 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 870E55ED2; Wed, 15 Feb 2006 00:14:27 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7c2a57e73ba0401177fa80b361b96d9b@web.de> Content-Transfer-Encoding: 7bit Cc: scsh-users@scsh.net From: RT Happe Subject: Re: how do I write "(a; b) >file" in scsh? Date: Wed, 15 Feb 2006 00:13:51 +0100 To: Wolfgang Hukriede X-Mailer: Apple Mail (2.623) Sender: rthappe@web.de X-Sender: rthappe@web.de Resent-Message-ID: <7vCdJD.A.KoU.SRm8DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/248 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 00:14:27 +0100 (MET) Wolfgang Hukriede wrote: > how do I write "(a; b) >file" in scsh? > > I came up with (run (begin (run (a)) (run (b))) (> file)) > but this looks a bit ridiculous, right? It does. If you can stand a conditional sequence, you may go for this also fairly ridiculous look: (&& (a) (epf (b) (> file))), e.g. (&& (sleep 5) (epf (ls) (> "foo.txt"))) rthappe From scsh-users-request@scsh.net Wed Feb 15 00:35:13 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 85D4B147; Wed, 15 Feb 2006 00:35:11 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40016-04; Wed, 15 Feb 2006 00:35:09 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id A4B83156; Wed, 15 Feb 2006 00:35:02 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id CEE255ED5; Wed, 15 Feb 2006 00:35:00 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Mime-Version: 1.0 (Apple Message framework v623) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: Scsh Users From: RT Happe Subject: Fwd: how do I write "(a; b) >file" in scsh? Date: Wed, 15 Feb 2006 00:34:29 +0100 X-Mailer: Apple Mail (2.623) Sender: rthappe@web.de X-Sender: rthappe@web.de Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/249 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 00:35:00 +0100 (MET) [ resend with the intended sender address ] > I wrote: > >> It does. If you can stand a conditional sequence, you may go for this >> also fairly ridiculous look: (&& (a) (epf (b) (> file))), e.g. >> >> (&& (sleep 5) (epf (ls) (> "foo.txt"))) > > .. which, however, loses the output of the first command (a). That > could > be captured with an excess of ridiculosity that I don't want to > recommend, > > (&& (epf (ls) (> "foo.txt")) > (epf (date) (>> "foo.txt"))) > > Probably I'm just experiencing pre-sleep dullness, or you may have to > build your own sequencing form. (The process notation is not beyond > criticism.) > > > rthappe From scsh-users-request@scsh.net Wed Feb 15 00:41:05 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8C0531255; Wed, 15 Feb 2006 00:41:03 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44400-05; Wed, 15 Feb 2006 00:40:56 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 1C8911334; Wed, 15 Feb 2006 00:40:49 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id F270E5ED5; Wed, 15 Feb 2006 00:40:47 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net X-Injected-Via-Gmane: http://gmane.org/ To: scsh-users@scsh.net From: dpeschel@eskimo.com (Derek Peschel) Subject: Commander-S -- where are handle-signal-default and ignore-signal defined? Date: Tue, 14 Feb 2006 23:32:34 +0000 (UTC) Organization: Eskimo North (206) For-Ever Lines: 46 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: eskimo.com User-Agent: slrn/0.9.5.7 (UNIX) Sender: news Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/250 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 00:40:47 +0100 (MET) Apparently this is the place for Commander-S support. I was fascinated to find out about Commander-S since I've been looking for a UI that knows about the structure of commands' output text. I haven't gotten it to work, however. For one thing, I'm getting these compiler warnings: Warning: undefined variables #{Package 286 jobs} handle-signal-default Warning: undefined variables #{Package 291 nuit} ignore-signal Then when I run the commander-s script from the build directory, I get heap size 5000000 is too small, using 6155008 starting remote handler for condition(exception 10 undefined-global #{Location 10804 ignore-signal nuit}) Please connect to port 8888 Debug messages will be on /dev/ttyqf (except my newsreader made me wrap the text -- I put a CR after the space after "Location") And if I connect to port 8888, I get Welcome to the command processor of the remote scsh #{Exception-continuation (pc 10) (run in nuit)} followed by a > prompt. Could these symptoms all reflect an out-of-date version of a package Commander-S depends on? My system has - Mac OS 10.3.7 - scsh 0.6.6 with the two patches from the Commander-S distribution - Commander-S from CVS, a few days ago - scsh-install-lib 1.2.0 - scsh-ncurses 1.0 - sunterlib from CVS, about the same day I got Commander-S There could be other problems... I am still learning about the Scheme48 package system, so the commands I built or ran everything with could be wrong. Let me know if more details would be helpful. Thanks, -- Derek From scsh-users-request@scsh.net Wed Feb 15 09:54:21 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 5B74E1325; Wed, 15 Feb 2006 09:54:19 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44518-03; Wed, 15 Feb 2006 09:54:15 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id CDD5111C1; Wed, 15 Feb 2006 09:54:08 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id C791C5ED2; Wed, 15 Feb 2006 09:54:07 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: Eric Knauel To: dpeschel@eskimo.com (Derek Peschel) Cc: scsh-users@scsh.net Subject: Re: Commander-S -- where are handle-signal-default and ignore-signal defined? In-Reply-To: (Derek Peschel's message of "Tue, 14 Feb 2006 23:32:34 +0000 (UTC)") References: Date: Wed, 15 Feb 2006 09:52:02 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) XEmacs/21.5-b22 (darwin) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/251 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 09:54:07 +0100 (MET) --=-=-= On Wed 15 Feb 2006 00:32, dpeschel@eskimo.com (Derek Peschel) writes: > Apparently this is the place for Commander-S support. I was fascinated > to find out about Commander-S since I've been looking for a UI that knows > about the structure of commands' output text. I haven't gotten it to work, > however. > > For one thing, I'm getting these compiler warnings: > > Warning: undefined variables > #{Package 286 jobs} > handle-signal-default > > Warning: undefined variables > #{Package 291 nuit} > ignore-signal Ah, I just realized that I didn't mention the third patch in Commander S's README that is needed to fix an off-the-shelf scsh 0.6.6. Here it is: --=-=-= --=-=-= Sorry for the inconvenience! > Then when I run the commander-s script from the build directory, I get > > heap size 5000000 is too small, using 6155008 > starting remote handler for condition(exception 10 undefined-global #{Location > 10804 ignore-signal nuit}) > Please connect to port 8888 > Debug messages will be on /dev/ttyqf > > (except my newsreader made me wrap the text -- I put a CR after the space > after "Location") And if I connect to port 8888, I get > > Welcome to the command processor of the remote scsh > #{Exception-continuation (pc 10) (run in nuit)} > > followed by a > prompt. Could these symptoms all reflect an out-of-date > version of a package Commander-S depends on? This error should go away after upgrading scsh. > My system has > > - Mac OS 10.3.7 > - scsh 0.6.6 with the two patches from the Commander-S distribution > - Commander-S from CVS, a few days ago > - scsh-install-lib 1.2.0 > - scsh-ncurses 1.0 > - sunterlib from CVS, about the same day I got Commander-S Looks good. Installing Commander S will be easier once scsh 0.6.7 is released... -Eric -- "Excuse me --- Di Du Du Duuuuh Di Dii --- Huh Weeeheeee" (Albert King) --=-=-=-- From scsh-users-request@scsh.net Wed Feb 15 13:36:17 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id BBB08188; Wed, 15 Feb 2006 13:36:14 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56118-02; Wed, 15 Feb 2006 13:36:08 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 5812519F; Wed, 15 Feb 2006 13:36:01 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 35F1A5ED5; Wed, 15 Feb 2006 13:36:00 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Cc: Derek Peschel Subject: Re: Commander-S -- where are handle-signal-default and ignore-signal defined? In-Reply-To: <20060215010845.B27419@eskimo.com> (Derek Peschel's message of "Wed, 15 Feb 2006 01:08:46 -0800") References: <20060215010845.B27419@eskimo.com> From: Eric Knauel Date: Wed, 15 Feb 2006 13:35:02 +0100 Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.5 (cucumber, darwin) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/252 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 13:36:00 +0100 (MET) --=-=-= On Wed 15 Feb 2006 10:08, Derek Peschel writes: > On Wed, Feb 15, 2006 at 09:52:02AM +0100, Eric Knauel wrote: >> Ah, I just realized that I didn't mention the third patch in Commander >> S's README that is needed to fix an off-the-shelf scsh 0.6.6. Here it >> is: > > And at that spot I see an empty attachment. Please send the patch > again. Second attempt: --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=commander-s-patch-3.diff Index: scsh/scsh-interfaces.scm =================================================================== RCS file: /cvsroot/scsh/scsh/scsh/scsh-interfaces.scm,v retrieving revision 1.55.2.6 retrieving revision 1.55.2.7 diff -u -r1.55.2.6 -r1.55.2.7 --- scsh/scsh-interfaces.scm 30 May 2005 12:59:05 -0000 1.55.2.6 +++ scsh/scsh-interfaces.scm 13 Sep 2005 13:14:16 -0000 1.55.2.7 @@ -437,9 +437,9 @@ (define-interface scsh-signals-interface (export signal-process signal-process-group - ;; JMG: this syscalls doesn't cooperate with the thread-system + ;; JMG: this syscall doesn't cooperate with the thread-system ;; pause-until-interrupt - itimer ;; now defined in low-interrupt as a artificial interrupt + itimer ;; now defined in low-interrupt as an artificial interrupt )) @@ -1061,6 +1061,9 @@ set-interrupt-handler interrupt-handler + ignore-signal + handle-signal-default + ;; reexported from low-interrupt interrupt/alrm interrupt/alarm interrupt/int interrupt/keyboard --=-=-= >> Looks good. Installing Commander S will be easier once scsh 0.6.7 is >> released... > > By the way, do you know how to increase the default heap size in Scheme48? > I tried something like "./configure CFLAGS=-DDEFAULT_HEAP_SIZE=6250000" > (the exact line isn't in my bash history, it seems) and then "make" and > "sudo make install" in the root of the scsh distribution. Unfortunately, it's not that simple. Actually, the file "bin/scsh" is a sh-script that runs the scsh virtual machine with a certain heap image. To make the vm allocate more heap add the command line argument "-h num" where num is the heap size in number of words to that line. For 32 MB heap, the Makefile line looks like this: echo 'exec $$lib/$(VM) -h 8388608 -i $$lib/$(IMAGE) "$$@"' \ However, if you want to run Commander S with more heap, you have to modify its install.scm. The variable IMAGE-HEADER contains the exec call for the scshvm, just add "-h num" there: (define image-header (format #f "#!~a/scsh/scshvm -h 8388608\\\n-o ~a/scsh/scshvm -i\n" (lib-dir) (lib-dir))) I think adding a command line option to the commander-s binary to specify the heap size is a good idea. I'll try to do that. > Then I reinstalled Commander-S. The warning from Commander-S still > appeared. I do need to make sure old copies of things aren't > hanging around (as I said, I'm still learning about the package > system, and my previous builds may have left files in places I > haven't cleaned out). Which warning? The warning about undefined variables or the warning concerning the heap size? -Eric -- "Excuse me --- Di Du Du Duuuuh Di Dii --- Huh Weeeheeee" (Albert King) --=-=-=-- From scsh-users-request@scsh.net Wed Feb 15 20:44:32 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 5A9B313D1; Wed, 15 Feb 2006 20:44:31 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25454-05; Wed, 15 Feb 2006 20:44:24 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 6AF5E13C3; Wed, 15 Feb 2006 20:44:22 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 1F0E15ED2; Wed, 15 Feb 2006 20:44:21 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=itHiojsTjsrY3xqmmAXB5uQHCGThokjhyR/Tmyds2zu7FXJGMSSAZoda1k4webydXxapSNLHOdwvSbIPhNKOGAXysSsKo9DR7hklQgt0Hs4rdoYRHfyyd1oGCRUBjZ3O2/GwveiAy8uOgjg0jHVbmD13zvxHWjYKQ7vriuQMXJc= ; Message-ID: <20060215194414.52100.qmail@web34303.mail.mud.yahoo.com> Date: Wed, 15 Feb 2006 11:44:14 -0800 (PST) From: Olwe Bottorff Subject: Newbie wonders "Why scsh?" To: scsh-users@scsh.net MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/253 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 15 Feb 2006 20:44:21 +0100 (MET) X-Spam-Status: No, hits=2.224 tagged_above=2 required=6.31 tests=[FORGED_RCVD_HELO=0.05, FORGED_YAHOO_RCVD=2.174] X-Spam-Level: ** I was poking around on Lambda the U and saw a discussion compare regular scripting to scsh scripting. The thread seemed to ask why bother with scsh? So I thought I'd ask the devot`tes what advantages you get from scripting in scsh? BTW I couldn't download the ps version of your manual. Olwe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From scsh-users-request@scsh.net Thu Feb 16 03:30:57 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id A2DFE13C9; Thu, 16 Feb 2006 03:30:55 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26494-05; Thu, 16 Feb 2006 03:30:52 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 0AD1713C3; Thu, 16 Feb 2006 03:30:51 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id F05C25ED2; Thu, 16 Feb 2006 03:30:49 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net In-Reply-To: <20060215194414.52100.qmail@web34303.mail.mud.yahoo.com> References: <20060215194414.52100.qmail@web34303.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <6f9eb1fbccca1b3c45d7f052056b3eb3@web.de> Content-Transfer-Encoding: 7bit Cc: scsh-users@scsh.net From: RT Happe Subject: Re: Newbie wonders "Why scsh?" Date: Thu, 16 Feb 2006 03:30:16 +0100 To: Olwe Bottorff X-Mailer: Apple Mail (2.623) Sender: rthappe@web.de X-Sender: rthappe@web.de Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/254 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 03:30:49 +0100 (MET) Olwe Bottorff wrote: > scsh? So I thought I'd ask the devot`tes what > advantages you get from scripting in scsh? BTW I That, or more or less that, was discussed in a thread following the monthly posting of the faq, cf. http://www.scsh.net/mail-archive/scsh-users/2003-01/threads.html#00021 > couldn't download the ps version of your manual. Seems to work for me. Perhaps a temporary server failure? rthappe From scsh-users-request@scsh.net Thu Feb 16 03:54:49 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 41BF213DE; Thu, 16 Feb 2006 03:54:47 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26512-01; Thu, 16 Feb 2006 03:54:41 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 5816213C3; Thu, 16 Feb 2006 03:54:36 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 3F8475ED5; Thu, 16 Feb 2006 03:54:35 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: scsh-users@scsh.net Content-Transfer-Encoding: 7bit From: Rick Hanson Subject: New scsh news? (Was "Re: Commander-S -- where are handle-signal-default ...") Date: Wed, 15 Feb 2006 21:50:54 -0500 To: Eric Knauel X-Mailer: Apple Mail (2.746.2) Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/255 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 03:54:35 +0100 (MET) On Feb 15, 2006, at 3:52 AM, Eric Knauel wrote: > > Looks good. Installing Commander S will be easier once scsh 0.6.7 is > released... > Since, you brought it up -- just curious: any guess as to when scsh 0.6.7 might be released? Thanks for any info, --Rick Chief of Scsh-Users List Lurkers :-) From scsh-users-request@scsh.net Thu Feb 16 08:50:30 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 53EB8106; Thu, 16 Feb 2006 08:50:27 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41680-01; Thu, 16 Feb 2006 08:50:20 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id CBA6B110; Thu, 16 Feb 2006 08:50:18 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id C08535ED2; Thu, 16 Feb 2006 08:50:17 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: Rick Hanson Cc: Eric Knauel , scsh-users@scsh.net Subject: Re: New scsh news? References: From: Martin Gasbichler Date: Thu, 16 Feb 2006 08:48:41 +0100 In-Reply-To: (Rick Hanson's message of "Wed, 15 Feb 2006 21:50:54 -0500") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/256 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 08:50:17 +0100 (MET) --=-=-= Rick Hanson writes: > On Feb 15, 2006, at 3:52 AM, Eric Knauel wrote: > >> >> Looks good. Installing Commander S will be easier once scsh 0.6.7 is >> released... >> > > Since, you brought it up -- just curious: any guess as to when scsh > 0.6.7 might be released? I hope to release it within the next four weeks. -- Martin --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBD9C5d2GQxKfWGs6MRAnHiAJ9KdT75+NQdOF0urzYB9V4b8ypG4ACfVEYZ GlRh16eTRJluPZY02x9ASE8= =vFv9 -----END PGP SIGNATURE----- --=-=-=-- From scsh-users-request@scsh.net Thu Feb 16 08:51:17 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 5F59E12E; Thu, 16 Feb 2006 08:51:16 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41680-03; Thu, 16 Feb 2006 08:51:13 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id DE424110; Thu, 16 Feb 2006 08:51:11 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id C8FA45ED5; Thu, 16 Feb 2006 08:51:11 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: Olwe Bottorff Cc: scsh-users Subject: Re: Newbie wonders "Why scsh?" References: <20060215194414.52100.qmail@web34303.mail.mud.yahoo.com> From: Martin Gasbichler Date: Thu, 16 Feb 2006 08:51:08 +0100 In-Reply-To: <20060215194414.52100.qmail@web34303.mail.mud.yahoo.com> (Olwe Bottorff's message of "Wed, 15 Feb 2006 11:44:14 -0800 (PST)") Message-ID: <0xr763zqqb.fsf@informatik.uni-tuebingen.de> User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/257 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 08:51:11 +0100 (MET) Olwe Bottorff writes: > I was poking around on Lambda the U and saw a > discussion compare regular scripting to scsh > scripting. Could you send me the URL of this discussion? -- Martin From scsh-users-request@scsh.net Thu Feb 16 18:32:26 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 0DD06122; Thu, 16 Feb 2006 18:32:25 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 52246-03; Thu, 16 Feb 2006 18:32:19 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 789E612E; Thu, 16 Feb 2006 18:32:15 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 631B55ED5; Thu, 16 Feb 2006 18:32:14 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Message-ID: <47068.192.153.92.254.1140111126.squirrel@www.tamos.net> In-Reply-To: References: Date: Thu, 16 Feb 2006 12:32:06 -0500 (EST) Subject: Re: New scsh news? From: "Rick Hanson" To: "Martin Gasbichler" Cc: scsh-users@scsh.net Reply-To: rick@tamos.net User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/258 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 18:32:14 +0100 (MET) > > I hope to release it within the next four weeks. > Sweeeet! Thanks a bunch, Martin! --Rick From scsh-users-request@scsh.net Thu Feb 16 19:00:58 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id CF7B9133F; Thu, 16 Feb 2006 19:00:57 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21420-05; Thu, 16 Feb 2006 19:00:50 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id E1741132B; Thu, 16 Feb 2006 19:00:47 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 9B1E95ED5; Thu, 16 Feb 2006 19:00:46 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=kTpSeCVo+MLw4oi8SmyxuC/CED/3oIH4D54CXwHPzetCpeuvxGXSq19NR6Lx/JgMkzSRKso4o0Ivg9NkAOSPZHr517IPGuNrgRpmdFXL0s8R/gPUXZmDv8Eh+TYwDKrKXXsQyGlPOxPIted4jsoGGJ+iYbXA50RM+1hYuZ2YYzo= ; Message-ID: <20060216180039.3867.qmail@web34313.mail.mud.yahoo.com> Date: Thu, 16 Feb 2006 10:00:39 -0800 (PST) From: Olwe Bottorff Subject: Local Home install? To: scsh users MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/259 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 19:00:46 +0100 (MET) X-Spam-Status: No, hits=2.224 tagged_above=2 required=6.31 tests=[FORGED_RCVD_HELO=0.05, FORGED_YAHOO_RCVD=2.174] X-Spam-Level: ** Is there a flag to set in the configure to do a $HOME install? I don't have root priv here at work on our Debian Sarges. Olwe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From scsh-users-request@scsh.net Thu Feb 16 23:14:04 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 0D714140C; Thu, 16 Feb 2006 23:14:02 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35566-01; Thu, 16 Feb 2006 23:13:59 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 1E12A1401; Thu, 16 Feb 2006 23:13:57 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 820275ED5; Thu, 16 Feb 2006 23:13:56 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net In-Reply-To: <20060216180039.3867.qmail@web34313.mail.mud.yahoo.com> References: <20060216180039.3867.qmail@web34313.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <351edbf60b3990085b26e02fce495f25@web.de> Content-Transfer-Encoding: 7bit Cc: scsh users From: RT Happe Subject: Re: Local Home install? Date: Thu, 16 Feb 2006 23:13:22 +0100 To: Olwe Bottorff X-Mailer: Apple Mail (2.623) Sender: rthappe@web.de X-Sender: rthappe@web.de Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/260 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 23:13:56 +0100 (MET) Olwe Bottorff wrote: > Is there a flag to set in the configure to do a $HOME > install? I don't have root priv here at work on our As the scsh-0.6.6/INSTALL file sez You can pass some additional options to the configure script, along them the installation directory with the --prefix=/my/install/location option. Type ./configure --help to get a list of all switches. rthappe From scsh-users-request@scsh.net Thu Feb 16 23:52:01 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8D04B140F; Thu, 16 Feb 2006 23:52:00 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 35334-05; Thu, 16 Feb 2006 23:51:50 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 1FD951383; Thu, 16 Feb 2006 23:51:46 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id B7A575ED7; Thu, 16 Feb 2006 23:51:44 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Kr3QF2sUAgey/MV6qdtravs6SdMMYAlDRRqA9Ejq4j6Ji9DhexKrWlDnK3ployMsXuo0M140Q4AUOY5sp6PmRYHTu23TIS7OSvyNqGq1sBuB25Chlar0f/D8ZD5XTnK7y15NRN4ecReJ00zew7y+Limv15gvDFMbksV2kkoKB7o= ; Message-ID: <20060216225137.35401.qmail@web34311.mail.mud.yahoo.com> Date: Thu, 16 Feb 2006 14:51:36 -0800 (PST) From: Olwe Bottorff Subject: "Newbie from Hell" To: scsh users MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/261 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 23:51:44 +0100 (MET) X-Spam-Status: No, hits=2.224 tagged_above=2 required=6.31 tests=[FORGED_RCVD_HELO=0.05, FORGED_YAHOO_RCVD=2.174] X-Spam-Level: ** Sorry for being the newbie from hell. I just got it installed per INSTALL directions...I am capable of reading INSTALL instructions... Olwe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From scsh-users-request@scsh.net Thu Feb 16 23:52:03 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id A66F21D7; Thu, 16 Feb 2006 23:52:02 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53464-03; Thu, 16 Feb 2006 23:51:54 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 2473E175; Thu, 16 Feb 2006 23:51:52 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 071355EF0; Thu, 16 Feb 2006 23:51:51 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FwH/DE8RvReW3nJ3+MStPEMDWuzrmtx930i8vk/QWEip84GkxrR54kh2uD0I6hJswudwqdg1/3X/ZSKctlS8m3YHrglJA6/o+wXhuam5Y6PYZHGCzVaA1pBQ//mYKJnGvJ4RLjLVLoHIhk8c9bNpfLE7HvgCmP1SOMYkvBHcBbk= ; Message-ID: <20060216225104.19840.qmail@web34310.mail.mud.yahoo.com> Date: Thu, 16 Feb 2006 14:51:04 -0800 (PST) From: Olwe Bottorff Subject: "Newbie from Hell" To: scsh users MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/262 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 16 Feb 2006 23:51:51 +0100 (MET) X-Spam-Status: No, hits=2.224 tagged_above=2 required=6.31 tests=[FORGED_RCVD_HELO=0.05, FORGED_YAHOO_RCVD=2.174] X-Spam-Level: ** Sorry for being the newbie from hell. I just got it installed per INSTALL directions...I am capable of reading INSTALL instructions... Olwe __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From scsh-users-request@scsh.net Fri Feb 17 10:30:44 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 638D8135; Fri, 17 Feb 2006 10:30:42 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 37526-05; Fri, 17 Feb 2006 10:30:40 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 72DA1192; Fri, 17 Feb 2006 10:30:38 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 5297F5ED5; Fri, 17 Feb 2006 10:30:37 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net X-Auth-Info: cY48hGVRLwxrM/pSK0Bc8ZPZdqg0qTtr9zqBT7uv1Dc= Date: Fri, 17 Feb 2006 10:36:41 +0100 From: PILCH Hartmut =?utf-8?B?6KO05a+S54mn?= To: scsh-users@scsh.net Subject: Re: New scsh news? Message-ID: <20060217093641.GA7152@wortIC.oas.a2e.de> References: <47068.192.153.92.254.1140111126.squirrel@www.tamos.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47068.192.153.92.254.1140111126.squirrel@www.tamos.net> User-Agent: Mutt/1.5.9i Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/263 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Fri, 17 Feb 2006 10:30:37 +0100 (MET) > > I hope to release it within the next four weeks. > > > > Sweeeet! Thanks a bunch, Martin! Is there any hope of getting utf-8 support in that release ? From scsh-users-request@scsh.net Fri Feb 17 10:35:57 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 6C8E0133F; Fri, 17 Feb 2006 10:35:55 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36540-01; Fri, 17 Feb 2006 10:35:51 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 19F851281; Fri, 17 Feb 2006 10:35:50 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id F31F35ED5; Fri, 17 Feb 2006 10:35:48 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: PILCH Hartmut =?gb2312?B?xeG6rsTB?= Cc: scsh-users@scsh.net Subject: Re: New scsh news? References: <47068.192.153.92.254.1140111126.squirrel@www.tamos.net> <20060217093641.GA7152@wortIC.oas.a2e.de> From: Martin Gasbichler Date: Fri, 17 Feb 2006 10:35:42 +0100 In-Reply-To: <20060217093641.GA7152@wortIC.oas.a2e.de> (PILCH Hartmut's message of "Fri, 17 Feb 2006 10:36:41 +0100") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b24 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: quoted-printable Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/264 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Fri, 17 Feb 2006 10:35:48 +0100 (MET) PILCH Hartmut =C5=E1=BA=AE=C4=C1 writes: > Is there any hope of getting utf-8 support in that release ? No, there will be no Unicode support in scsh until we replace the underlying Scheme 48 implementation by a newer version which requires a lot of effort and time. --=20 Martin From scsh-users-request@scsh.net Sat Feb 18 20:02:56 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 84A11138; Sat, 18 Feb 2006 20:02:54 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17616-02; Sat, 18 Feb 2006 20:02:50 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 1018212C; Sat, 18 Feb 2006 20:02:49 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 07BD15ECE; Sat, 18 Feb 2006 20:02:48 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Sat, 18 Feb 2006 20:02:40 +0100 From: Lionel Elie Mamane To: scsh-users@scsh.net Subject: SCSH status and future Message-ID: <20060218190240.GA13741@capsaicin.mamane.lu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: GNU/Linux X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc User-Agent: Mutt/1.5.11+cvs20060126 Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/265 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sat, 18 Feb 2006 20:02:48 +0100 (MET) Hi, Until a few months ago, I was a quite happy user of scsh. (I'm also the main maintainer of the Debian package of scsh.) Any script I was doing (that didn't have to be embedded in a Makefile) for my own use was done in scsh. Both long term scripts (e.g. backup) or throw-away (just typed on the command line, executed once and never saved). I was dreaming of scsh every time I was forced to write a serious bash (or even worse - POSIX /bin/sh) script. But in a short time, this all changed. The machine I backup _to_ is now an amd64 machine. I cannot use scsh for my backup scripts now. My main desktop is also a amd64 machine. I cannot use scsh for my throw-away execute-once scripts. And I don't know of a good replacement. (I removed features from my backup script to shoehorn it into guile + a compatibility layer.) Unless scsh gets portability to 64 bits machines on the middle term, I think it will slowly fade into oblivion. It would be a shame. Anybody wants to make an scsh (_with_ the process notation) on top of another scheme than the old scheme48 it is now based on? -- Lionel From scsh-users-request@scsh.net Sat Feb 18 20:07:33 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 90B1D137E; Sat, 18 Feb 2006 20:07:31 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33938-01; Sat, 18 Feb 2006 20:07:25 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 6B15D135E; Sat, 18 Feb 2006 20:07:19 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 5F0525ED5; Sat, 18 Feb 2006 20:07:18 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Sat, 18 Feb 2006 20:07:12 +0100 From: Lionel Elie Mamane To: scsh-users@scsh.net Subject: Re: SCSH status and future Message-ID: <20060218190712.GA13963@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060218190240.GA13741@capsaicin.mamane.lu> X-Operating-System: GNU/Linux X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc User-Agent: Mutt/1.5.11+cvs20060126 Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/266 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sat, 18 Feb 2006 20:07:18 +0100 (MET) On Sat, Feb 18, 2006 at 08:02:40PM +0100, Lionel Elie Mamane wrote: > (I removed features from my backup script to shoehorn it into guile > + a compatibility layer.) I had already removed features to work around the lack of support of large files (64 bit C off_t type) in scsh. These features are now back in with the switch to guile. -- Lionel From scsh-users-request@scsh.net Sat Feb 18 23:42:08 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id F39F51324; Sat, 18 Feb 2006 23:42:05 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23478-03; Sat, 18 Feb 2006 23:41:59 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id B04F112E4; Sat, 18 Feb 2006 23:41:57 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id AD5695ED2; Sat, 18 Feb 2006 23:41:56 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Sat, 18 Feb 2006 23:41:49 +0100 From: Lionel Elie Mamane To: Daniel Hagerty Cc: scsh-users@scsh.net Subject: Re: SCSH status and future Message-ID: <20060218224149.GB14770@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17399.38634.713594.377273@perdition.linnaean.org> X-Operating-System: GNU/Linux X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc User-Agent: Mutt/1.5.11+cvs20060126 Resent-Message-ID: <6skwLB.A.qjE.zK69DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/267 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sat, 18 Feb 2006 23:41:56 +0100 (MET) On Sat, Feb 18, 2006 at 04:51:38PM -0500, Daniel Hagerty wrote: > > I had already removed features to work around the lack of support > > of large files (64 bit C off_t type) in scsh. These features are > > now back in with the switch to guile. > I doubt your problem is actually 64 bit off_t, but something > more subtle. My OS has had 64 bit off_t on 32 bit systems for a > decade. scsh works without problems except for the usual caveats > for something that will only allow less that 31 bits at lseek and > friends. And stat(). Just create a > 2GB file and try to get its size. Your scsh script aborts with an error. That's the "usual caveats". It keeps me from using scsh to delete files of size 0 in a directory containing other (big) files. Pretty limiting. > As for general lack of 64 bit cleanliness, you probably don't need > 64 bits worth of addressing from your scripting language. While it > would be more reasonable if it did (gratuitous limits are bad), in > practice, you will probably find that you're using the wrong tool for > the job long before you hit address space limitations. Is there any > reason why you can't build scsh as a 32 bit binary? I have to compile the libraries it needs as a 32 bit binary first. While theoretically possible, having a distribution packaging system that supports the multiple architectures supported by the hardware is not there yet. (And conflicts with LSB support and that kind of boring things.) -- Lionel From scsh-users-request@scsh.net Sun Feb 19 02:40:33 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id BA3621341; Sun, 19 Feb 2006 02:40:31 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 33982-05; Sun, 19 Feb 2006 02:40:27 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 2B5FD12C0; Sun, 19 Feb 2006 02:40:26 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 24CDA5ED2; Sun, 19 Feb 2006 02:40:25 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net X-Injected-Via-Gmane: http://gmane.org/ To: scsh-users@scsh.net From: dpeschel@eskimo.com (Derek Peschel) Subject: Can an input editor control the scsh reader? Date: Sun, 19 Feb 2006 01:40:04 +0000 (UTC) Organization: Eskimo North (206) For-Ever Lines: 53 Message-ID: X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: eskimo.com User-Agent: slrn/0.9.5.7 (UNIX) Sender: news Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/268 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sun, 19 Feb 2006 02:40:25 +0100 (MET) Sorry if this is the wrong place to ask. It could be a Scheme48 question, though it also could lead to a change in Commander-S which specifically uses scsh. By "input editor" I mean a feature that allows S-expression input to be edited while the user is typing it in. A useful editor has many other features, but I'm not asking about them. My hypothetical input editor works with chunks. A chunk may be - one line containing one S-expression - one line containing multiple S-expressions - multiple lines containing one S-expression - multiple lines containing multiple S-expressions A chunk is a whole number of lines. A chunk is as short as possible; the only way to extend an S-expression onto a second line is to have unclosed parentheses at the end of the first. I believe my definition of chunk is the unit SLIME works with. The problems of blank input lines, or chunks with extra closing parentheses at the end, I'll deal with later. I'd like the editor to use the same grammar as scsh and Scheme48. The easiest way to do that is to get the current parser state from scsh after sending each line, either "complete" or "error". Is that possible? Extra state would be nice, such as locations of matching parens or other parts of the syntax tree or the nature and location of any error. Also, scsh must allow the editor to cancel the entire chunk. This is easy for chunks that hold one S-expression, but might be harder for chunks that hold more. Is it possible for an S-expression to be evaluated during the read process and affect the syntax of later S-expressions? (maybe a macro definition) If so, I can only think of compromise solutions: - make arrangements to unexecute expressions, which is much harder than unreading - weaken the rules about what can be unread when the user pushes the "cancel" key -- unread only back to the last incomplete expression - read S-expressions (possibly waiting for a space, return, etc. after the last paren or atom component) instead of lines - use a grammar that is only partly correct, and have the editor decide to pass the whole chunk to scsh (or not to, if the user cancels) Thanks for your help, -- Derek From scsh-users-request@scsh.net Sun Feb 19 04:15:36 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id C66A012E4; Sun, 19 Feb 2006 04:15:33 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43060-04; Sun, 19 Feb 2006 04:15:27 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 21031130C; Sun, 19 Feb 2006 04:15:25 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 00AB75ED5; Sun, 19 Feb 2006 04:15:23 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: William Xu To: scsh-users@scsh.net Subject: Re: SCSH status and future Organization: the Church of Emacs References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> Date: Sun, 19 Feb 2006 11:15:52 +0800 In-Reply-To: <20060218190712.GA13963@capsaicin.mamane.lu> (Lionel Elie Mamane's message of "Sat, 18 Feb 2006 20:07:12 +0100") Message-ID: <87bqx43uon.fsf@www.williamxu.com> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <2tm8O.A.C9E.LL-9DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/269 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sun, 19 Feb 2006 04:15:23 +0100 (MET) Lionel Elie Mamane writes: > On Sat, Feb 18, 2006 at 08:02:40PM +0100, Lionel Elie Mamane wrote: > >> (I removed features from my backup script to shoehorn it into guile >> + a compatibility layer.) > > I had already removed features to work around the lack of support of > large files (64 bit C off_t type) in scsh. These features are now back > in with the switch to guile. I'd really love scsh to be incorporated into guile project... -- William From scsh-users-request@scsh.net Sun Feb 19 08:27:12 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id AE1F2129; Sun, 19 Feb 2006 08:27:10 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20208-04; Sun, 19 Feb 2006 08:27:07 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 54F09121; Sun, 19 Feb 2006 08:27:06 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 25F075ED2; Sun, 19 Feb 2006 08:27:05 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Sun, 19 Feb 2006 08:26:56 +0100 From: Lionel Elie Mamane To: Daniel Hagerty Cc: scsh-users@scsh.net Subject: Re: SCSH status and future Message-ID: <20060219072656.GA1894@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> <20060218224149.GB14770@capsaicin.mamane.lu> <17399.48129.759286.213920@perdition.linnaean.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17399.48129.759286.213920@perdition.linnaean.org> X-Operating-System: GNU/Linux X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc User-Agent: Mutt/1.5.11+cvs20060126 Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/270 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sun, 19 Feb 2006 08:27:05 +0100 (MET) On Sat, Feb 18, 2006 at 07:29:53PM -0500, Daniel Hagerty wrote: > This is supposed to be informative, not a flame war. Please don't > assume you're being flamed; I just don't care that much about scsh. >> And stat(). Just create a > 2GB file and try to get its size. Your >> scsh script aborts with an error. That's the "usual caveats". It >> keeps me from using scsh to delete files of size 0 in a directory >> containing other (big) files. Pretty limiting. > (delete-file "flob") where flob is in excess of 2 gigs works for > me, as does deleting a zero length file in directories containing > large files. I cannot _test_ whether the file has zero size. Except by parsing the output of (run (ls)) or something like that... > At least on the system I'm on, rather than doing > something semi-rational like throwing a scheme level error, (which it does for me: Error: 75 "Value too large for defined data type" #{Procedure 13546 (stat-file in scsh-level-0)} "large_file" #t ) > file-info:size on a large file returns a number truncated into a > signed 32 bit quantity. > State code that doesn't work for you rather than making english > statements that are highly ambiguous. (for-each (lambda (f) (if (equal? (file-size f) 0) (delete-file f))) (directory-files)) But also (file-exists? "large_file") where large_file is the name of a large file. While throwing a scheme error on (file-size "large_file") is the most reasonable thing to do if you can't handle the number, I tend to think that from the user's point of view, there is no good reason for "file-exists?" to fail. (The reason is, I think, that scsh doesn't merely check for file existence, but does a full stat() call, parsing the results and caches them, under the assumption you are likely to ask some information on the file next. Not unreasonable, but gives surprising results in this case.) I actually worked around this one with (define (file-exists? fname) (member fname (directory-files))) > If it was throwing a scheme error, this should be catchable by the > normal means Yes, I could do that, indeed. >> I have to compile the libraries it needs as a 32 bit binary >> first. While theoretically possible, having a distribution packaging >> system that supports the multiple architectures supported by the >> hardware is not there yet. (And conflicts with LSB support and that >> kind of boring things.) > Thinly veiled flames are not conducive to getting people to > volunteer to help you. Sorry you felt flamed. Wasn't my intention. > If LSB says "thou shalt only provide 64 bit libraries to your > users" on a mixed 32/64 arch like amd64, It doesn't exactly say that, but its requirements for 32 bit binaries and 64 bit binaries conflict, if I remember well. Like they both can expect their libraries to dlopen() to be in /usr/lib/ or something like that. Only on some 64 bit architectures. Not all of them. I don't remember the details. > you are doing your users a disservice by specifying the standard as > such You are doing one subset of users a disservice and another set of users a service: Those that want to run binaries not specifically prepared for your distribution, but against the standard. > Insisting that a 64 bit flag day is a good idea doesn't seem to fly > for a lot of people. Yes. -- Lionel From scsh-users-request@scsh.net Sun Feb 19 08:42:47 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 8F198121; Sun, 19 Feb 2006 08:42:45 +0100 (MET) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28758-03; Sun, 19 Feb 2006 08:42:43 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id CCBF611B; Sun, 19 Feb 2006 08:42:41 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id B576A5ED2; Sun, 19 Feb 2006 08:42:40 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Sun, 19 Feb 2006 08:42:33 +0100 From: Lionel Elie Mamane To: William Xu Cc: scsh-users@scsh.net Subject: Re: SCSH status and future Message-ID: <20060219074233.GA2055@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <87bqx43uon.fsf@www.williamxu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87bqx43uon.fsf@www.williamxu.com> X-Operating-System: GNU/Linux X-Request-PGP: http://www.mamane.lu/openpgp/rsa_v4_4096.asc User-Agent: Mutt/1.5.11+cvs20060126 Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/271 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sun, 19 Feb 2006 08:42:40 +0100 (MET) On Sun, Feb 19, 2006 at 11:15:52AM +0800, William Xu wrote: > Lionel Elie Mamane writes: >> On Sat, Feb 18, 2006 at 08:02:40PM +0100, Lionel Elie Mamane wrote: >>> (I removed features from my backup script to shoehorn it into guile >>> + a compatibility layer.) >> I had already removed features to work around the lack of support of >> large files (64 bit C off_t type) in scsh. These features are now back >> in with the switch to guile. > I'd really love scsh to be incorporated into guile project... There is actually a partial port of the scsh 0.5 interfaces that doesn't seem to be maintained much anymore. It doesn't include the process notation. http://arglist.com/guile/ -- Lionel From scsh-users-request@scsh.net Sun Feb 19 11:47:39 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id D19AD13B7; Sun, 19 Feb 2006 11:47:37 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43074-03; Sun, 19 Feb 2006 11:47:32 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id C520B1353; Sun, 19 Feb 2006 11:47:27 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id CE2AD5ED2; Sun, 19 Feb 2006 11:47:26 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: Michael Sperber To: dpeschel@eskimo.com (Derek Peschel) Cc: scsh-users@scsh.net Subject: Re: Can an input editor control the scsh reader? References: Date: Sun, 19 Feb 2006 11:47:15 +0100 In-Reply-To: (Derek Peschel's message of "Sun, 19 Feb 2006 01:40:04 +0000 (UTC)") Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.5-b24 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: ClamAV using ClamSMTP Content-Transfer-Encoding: quoted-printable Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/272 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Sun, 19 Feb 2006 11:47:26 +0100 (MET) All of what you want is possible, but none of it is currently implemented. I'm not sure what exactly you're asking---if you need help with a specific item on your list, let us know and we'll try our best. --=20 Cheers =3D8-} Mike Friede, V=F6lkerverst=E4ndigung und =FCberhaupt blabla From scsh-users-request@scsh.net Mon Feb 20 15:30:16 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id B588A11AF; Mon, 20 Feb 2006 15:30:14 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29924-04; Mon, 20 Feb 2006 15:30:10 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id DDFF71237; Mon, 20 Feb 2006 15:30:06 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id CAA1B5ED5; Mon, 20 Feb 2006 15:30:05 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: William Xu To: scsh-users@scsh.net Subject: Re: SCSH status and future Organization: the Church of Emacs References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <87bqx43uon.fsf@www.williamxu.com> <20060219074233.GA2055@capsaicin.mamane.lu> Date: Mon, 20 Feb 2006 22:30:34 +0800 In-Reply-To: <20060219074233.GA2055@capsaicin.mamane.lu> (Lionel Elie Mamane's message of "Sun, 19 Feb 2006 08:42:33 +0100") Message-ID: <87bqx2w19x.fsf@www.williamxu.com> User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/273 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Mon, 20 Feb 2006 15:30:05 +0100 (MET) Lionel Elie Mamane writes: >> I'd really love scsh to be incorporated into guile project... > > There is actually a partial port of the scsh 0.5 interfaces that > doesn't seem to be maintained much anymore. It doesn't include the > process notation. http://arglist.com/guile/ Yes..that's why i'm complaining...it's quite a waste of time porting it to guile, anyway. Not to mention that it already causes some incompatibility errors with recent guile. -- William From scsh-users-request@scsh.net Mon Feb 20 17:51:06 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 59FEA13A4; Mon, 20 Feb 2006 17:51:04 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29196-05; Mon, 20 Feb 2006 17:50:58 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 393CD12E2; Mon, 20 Feb 2006 17:50:54 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 3125A5ED2; Mon, 20 Feb 2006 17:50:52 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: patch for io.c: scsh won't build with gcc 4.0.2 From: George Demmy Date: Mon, 20 Feb 2006 11:50:37 -0500 Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/274 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Mon, 20 Feb 2006 17:50:52 +0100 (MET) I've been playing with scsh since the early 0.5 days, so imagine my surprise when a routine configure; make ; make install for 0.6.6 blew up on a Fedora 4 box. The problem is with c/unix/io.c. gcc 4.0.2 doesn't like the storage class specification for the declaration of write_integer in ps_write_integer (and I don't blame it). Also, it's freaking out about type mismatches arisiing from mixed use of singed and unsigned longs. I've checked the CVS sources out, and get the same problem. I've included a patch that fixes the problem. The fix is simple: I moved the definition of write_integer above ps_write_integer, and nuked the internal declaration. I've also dropped the unsigned specifier. since ps_write_integer consumes signed longs, and this is the only function I can find that uses write_integer, this should not cause a problem. Kindest regards, G --- scsh/c/unix/io.c 2006-02-20 11:05:52.000000000 -0500 +++ patch/c/unix/io.c 2006-02-20 10:52:06.000000000 -0500 @@ -146,13 +146,27 @@ return 0; } } +static long +write_integer(long n, FILE *port) +{ + char ch; + long status; + + if (n == 0) + status = 0; + else { + status = write_integer(n / 10, port); + if (status == 0) { + ch = (n % 10) + '0'; + WRITE_CHAR(ch, port,status); } } + return status; +} + long ps_write_integer(long n, FILE *port) { int status; - static long write_integer(unsigned long n, FILE *port); - if (n == 0) { WRITE_CHAR('0', port, status); return status; } @@ -166,22 +180,6 @@ return status; } } -static long -write_integer(unsigned long n, FILE *port) -{ - char ch; - long status; - - if (n == 0) - status = 0; - else { - status = write_integer(n / 10, port); - if (status == 0) { - ch = (n % 10) + '0'; - WRITE_CHAR(ch, port,status); } } - return status; -} - long ps_write_string(char *string, FILE *port) { From scsh-users-request@scsh.net Tue Feb 21 02:30:59 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 9A325130F; Tue, 21 Feb 2006 02:30:57 +0100 (MET) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25916-03; Tue, 21 Feb 2006 02:30:54 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id A3D56139D; Tue, 21 Feb 2006 02:30:52 +0100 (MET) Received: by www.scsh.net (Postfix, from userid 3123) id 30AE75ED5; Tue, 21 Feb 2006 02:30:51 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net Date: Mon, 20 Feb 2006 20:30:29 -0500 From: Anthony Carrico To: scsh Subject: [RELEASE] Sunterlib 0.8 Message-ID: <20060221013029.GA25479@memebeam.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=_jvb.vm.bytemark.co.uk-21727-1140485450-0001-2" Content-Disposition: inline User-Agent: Mutt/1.5.11 Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/275 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Tue, 21 Feb 2006 02:30:51 +0100 (MET) This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_jvb.vm.bytemark.co.uk-21727-1140485450-0001-2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm pleased to announce version 0.8 of the Scheme Untergrund Library (sunterlib). Sunterlib hosts contributed libraries for Scheme 48 and Scsh. We plan to move to scsh install lib version 1.3.0 for release 0.9. Project web site: http://www.scsh.net/resources/sunterlib.html Current release: http://download.savannah.nongnu.org/releases/sunterlib/sunterlib-0.8.tar.= gz http://download.savannah.nongnu.org/releases/sunterlib/sunterlib-0.8.tar.= gz.sig NEWS (does not include individual library NEWS) version 0.8 2006-02-18 * Use install lib version 1.2.0 * Automatically check if libraries' NEWS and pkg-def.scm versions match. * New s48 library: riatables NEW S48 LIBRARIES riatables: rich hash tables. Public Domain 2005 Taylor Campbell Sunterlib is hosted at savannah: http://savannah.nongnu.org/projects/sunterlib/ The project site offers cvs access to the source code and a bug tracking system. Sunterlib already hosts packages from several authors; you may contribute your own packages to this library too. Please contact one the project administrators if you are interested. --=20 Anthony Carrico http://giftfile.org --=_jvb.vm.bytemark.co.uk-21727-1140485450-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFD+m00sYhrnH7Qa1wRAoQkAJoCJRIpSKRq+km27uabkvnRSR0mjwCeK0ay cMs5Ax+6DQsTYTeDHAZSI/s= =n8fL -----END PGP SIGNATURE----- --=_jvb.vm.bytemark.co.uk-21727-1140485450-0001-2-- From scsh-users-request@scsh.net Wed Feb 22 19:46:22 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id C864C11B; Wed, 22 Feb 2006 19:46:19 +0100 (NFT) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23388-01; Wed, 22 Feb 2006 19:46:09 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id B819112B; Wed, 22 Feb 2006 19:46:07 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id F0B905ED1; Wed, 22 Feb 2006 19:46:05 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060218190712.GA13963@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sat, 18 Feb 2006 22:51:56 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/276 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:46:05 +0100 (MET) > I had already removed features to work around the lack of support of > large files (64 bit C off_t type) in scsh. These features are now back > in with the switch to guile. I doubt your problem is actually 64 bit off_t, but something more subtle. My OS has had 64 bit off_t on 32 bit systems for a decade. scsh works without problems except for the usual caveats for something that will only allow less that 31 bits at lseek and friends. scsh will do the right thing with (seek foo 2147483647), but (seek foo 2147483648) throws a type error. (seek foo 2147483647) followed by (write-string "lets-go-past-the-barrier" foo) writes the string with no trouble, despite producing a file that's larger than 2^31. This is pretty common behavior. Something is preventing bigger numbers from getting to the C layer. As for general lack of 64 bit cleanliness, you probably don't need 64 bits worth of addressing from your scripting language. While it would be more reasonable if it did (gratuitous limits are bad), in practice, you will probably find that you're using the wrong tool for the job long before you hit address space limitations. Is there any reason why you can't build scsh as a 32 bit binary? From scsh-users-request@scsh.net Wed Feb 22 19:46:59 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 3161B179; Wed, 22 Feb 2006 19:46:58 +0100 (NFT) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23388-05; Wed, 22 Feb 2006 19:46:51 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 55B2B12B; Wed, 22 Feb 2006 19:46:48 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 381E15ECF; Wed, 22 Feb 2006 19:46:48 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060218224149.GB14770@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> <20060218224149.GB14770@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sun, 19 Feb 2006 01:30:01 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/277 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:46:48 +0100 (MET) This is supposed to be informative, not a flame war. Please don't assume you're being flamed; I just don't care that much about scsh. There was some amount of effort to port the scsh api to mzscheme, but I don't know where that stands; last I knew it was hung up on getting FFI more standardized. I'm not aware of anybody having volunteered to rewrite the C glue into yet another FFI du jour. > And stat(). Just create a > 2GB file and try to get its size. Your > scsh script aborts with an error. That's the "usual caveats". It keeps > me from using scsh to delete files of size 0 in a directory containing > other (big) files. Pretty limiting. (delete-file "flob") where flob is in excess of 2 gigs works for me, as does deleting a zero length file in directories containing large files. At least on the system I'm on, rather than doing something semi-rational like throwing a scheme level error, file-info:size on a large file returns a number truncated into a signed 32 bit quantity. State code that doesn't work for you rather than making english statements that are highly ambiguous. I can't figure out the precise failure case you mean for what you are being prevented from deleting zero size files for. If it was throwing a scheme error, this should be catchable by the normal means -- thus, why such behavior is considered dimly "reasonable" whereas truncation/aliasing like I'm seeing is not. file:size on a file of length 8589934595 returns 3, which is bad. > I have to compile the libraries it needs as a 32 bit binary > first. While theoretically possible, having a distribution packaging > system that supports the multiple architectures supported by the > hardware is not there yet. (And conflicts with LSB support and that > kind of boring things.) Thinly veiled flames are not conducive to getting people to volunteer to help you. If LSB says "thou shalt only provide 64 bit libraries to your users" on a mixed 32/64 arch like amd64, you are doing your users a disservice by specifying the standard as such and insisting that such a standard has any basis on reality. Fix the standard. If your packaging system can't deal with this mix, your packaging system is broken and you should address this. 32 vs 64 bit backwards compatability issues aren't new with amd64. Others have addressed this in ways that allow you to move on to more interesting problems and run what you need without a flag day; examine the prior art. Insisting that a 64 bit flag day is a good idea doesn't seem to fly for a lot of people. My employer has a hell of a lot of code that doesn't port cleanly to 64 bit systems (since we ran into the practical limitations of 32 bits a long time ago and got "clever"). We seem to be able to do coexistance of 32 and 64 bit code in a straight forward enough fashion without volunteering to compile a large body of code starting from the C library on up ourselves (and even when we do have to compile it ourselves, we can). Choose where your priorities are, because as it stands right now your requirements have mutual exclusivity problems. AFAICT, scheme48 still doesn't run on the alpha, which bodes poorly for you getting scsh/scheme48 functioning the way you want any time soon. Addressing your problems with 64 bit off_t is probably much simpler, but I'm not exactly volunteering myself at this rate. From scsh-users-request@scsh.net Wed Feb 22 19:48:00 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 158FE12B; Wed, 22 Feb 2006 19:47:59 +0100 (NFT) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23390-03; Wed, 22 Feb 2006 19:47:55 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id C77A1110; Wed, 22 Feb 2006 19:47:53 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id B3BE25ECF; Wed, 22 Feb 2006 19:47:53 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <17399.48129.759286.213920@perdition.linnaean.org> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> <20060218224149.GB14770@capsaicin.mamane.lu> <17399.48129.759286.213920@perdition.linnaean.org> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sun, 19 Feb 2006 03:33:08 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <9KbpkD.A.IAB.YHL_DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/278 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:47:53 +0100 (MET) > Addressing your problems with 64 bit off_t is probably much > simpler, but I'm not exactly volunteering myself at this rate. Well, I lied, my curiousity gets the better of me (a standard problem for getting me to do something "I don't care about"). I would not hold my breath on scheme48 ever moving into the nineties. The current version's FFI has no concept of a quad, to say nothing of whatever version scsh is based on. I'd expect to find the broader code riddled with issues, some of them annoying. This is not a show stopper for the problem of 64 bit off_t. There's more than one hammer, but the cleanest solution for moving 64 bit integers from C to scheme48 and back is probably as a byte vector (see the scheme48 docs). There are several minor implementation chocies to be made, but it looks like you can get there such that scheme can see 64 bit long bignums, and C sees a quad. Maybe I'll volunteer. It's low key and I could use the refresher course, being rusty. Inadequate large file support was passe in 1998, and this doesn't look hard. 48-96 hours of wallclock time *if* I can motivate myself. From scsh-users-request@scsh.net Wed Feb 22 19:48:25 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 3A7061300; Wed, 22 Feb 2006 19:48:23 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36676-02; Wed, 22 Feb 2006 19:48:21 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 6CAC712C0; Wed, 22 Feb 2006 19:48:19 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 4D7D95ECF; Wed, 22 Feb 2006 19:48:19 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060219072656.GA1894@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> <20060218224149.GB14770@capsaicin.mamane.lu> <17399.48129.759286.213920@perdition.linnaean.org> <20060219072656.GA1894@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sun, 19 Feb 2006 22:16:46 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/279 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:48:19 +0100 (MET) > I cannot _test_ whether the file has zero size. Except by parsing the > output of (run (ls)) or something like that... > > > At least on the system I'm on, rather than doing > > something semi-rational like throwing a scheme level error, > > (which it does for me: > > Error: 75 > "Value too large for defined data type" > #{Procedure 13546 (stat-file in scsh-level-0)} > "large_file" > #t > ) That's very catchable if I'm reading it correctly. That's the correct number and text to be EOVERFLOW on linux. You won't be able to tell how large the large file is, but you can tell that it's large. As a guess, your ability to do this is specifically dependant on off_t being a 32 bit quantity, and the kernel knowing that you're using a version of stat that is only capable of representing 32 bit sizes. This would explain why I see the wrong thing where you see the right thing. scsh is expressly using an FFI function that deals in longs, which will do the wrong thing on a system where off_t is inherently 64 bits. > But also > > (file-exists? "large_file") stat is the pretty much the standard method to determine if a file really exists. Reading a directory doesn't account for the case of a broken symlink. The file will "exist" as far as the directory entry is concerned, but isn't backed by anything real. There are probably other cases, but this one leaps to mind. From scsh-users-request@scsh.net Wed Feb 22 19:49:21 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id C72C21300; Wed, 22 Feb 2006 19:49:19 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36676-05; Wed, 22 Feb 2006 19:49:15 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id E3A9512C0; Wed, 22 Feb 2006 19:49:12 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id B86265ECF; Wed, 22 Feb 2006 19:49:12 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060219072656.GA1894@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <17399.38634.713594.377273@perdition.linnaean.org> <20060218224149.GB14770@capsaicin.mamane.lu> <17399.48129.759286.213920@perdition.linnaean.org> <20060219072656.GA1894@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sun, 19 Feb 2006 22:17:11 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/280 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:49:12 +0100 (MET) > > Thinly veiled flames are not conducive to getting people to > > volunteer to help you. > > Sorry you felt flamed. Wasn't my intention. Apologies. Written text is a lousy language for the non-verbal part of communication. The LSB comment read to me as being faux "polite", and this will annoy me greatly. The fact that LSB is being used as a justification for what appears to be broken behavior doesn't help. > It doesn't exactly say that, but its requirements for 32 bit binaries > and 64 bit binaries conflict, if I remember well. Like they both can > expect their libraries to dlopen() to be in /usr/lib/ or something > like that. Only on some 64 bit architectures. Not all of them. I don't > remember the details. This is not a conflict given engineering effort. 32 bit binaries and 64 bit binaries are distinguishable from one another, and your kernel can take appropriate steps to get them to coexist. It might help you to remember that amd64 is not the first platform to have these sorts of issues; sparcv9 is a decade old and presented similar problems with sparcv8 executables. NetBSD's techniques for dealing with this is one example of how to work around the problems. Only truly native binaries get the obvious treatment for accessing the filesystem. Other emulation targets (where a 32 bit binary on a 64 bit system is considered an emulation target, as is a.out on an ELF system) has its path lookup process intefered with. Opening /usr/lib/libcurses.so will actually attempt to open /emul/$foo/usr/lib/libncurses.so before trying the root of the filesystem ($foo being something appropriate for the binary type, like linux, netbsd32, aout, ibcs2, svr4_32, etc). So a linux binary can be presented with the libraries it needs without interfering with others; not to mention extending to other issues like incomptability between ld.so.conf formats. It's not perfect, but it does let you move on. > You are doing one subset of users a disservice and another set of > users a service: Those that want to run binaries not specifically > prepared for your distribution, but against the standard. I get to have my cake and eat it too and expect no less when the underlying capability is a simple matter of engineering. My web browser is a linux binary expecting an LSB compliant system. My system isn't LSB compliant and has no hope of doing so in reality. But my web browser sees LSB. From scsh-users-request@scsh.net Wed Feb 22 19:50:00 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 3540B12B; Wed, 22 Feb 2006 19:49:59 +0100 (NFT) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23392-05; Wed, 22 Feb 2006 19:49:55 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 16068110; Wed, 22 Feb 2006 19:49:53 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 005455ECD; Wed, 22 Feb 2006 19:49:52 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060219074233.GA2055@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> <87bqx43uon.fsf@www.williamxu.com> <20060219074233.GA2055@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Sun, 19 Feb 2006 22:46:54 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <5zoYAC.A.RCB.PJL_DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/281 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:49:52 +0100 (MET) > There is actually a partial port of the scsh 0.5 interfaces that > doesn't seem to be maintained much anymore. It doesn't include the > process notation. http://arglist.com/guile/ EPF is just a macro layer. The part that's hard about full scsh is that it expects a full posix layer at the bottom, which few schemes make any attempt to support. So the FFI problem appears, and AFAIK, standardized FFI hasn't happened yet; it's still somewhere in uncompleted SRFI land. scsh uses a lot of FFI glue, and its macros are mostly written in clinger-reese, which never gained much traction. Many of EPF's corner cases are likely to interact with posix features you might not find, but you should be able to figure out what those problems are as you flesh out a sketch of it. Chicken leaps to mind as probably the easiest implementation for somebody that doesn't want to jump through numerous recursive lossage hoops. It's got a posix layer, modern macro system, and FFI for any low level posix features that are missing. Compiles to C to boot. From scsh-users-request@scsh.net Wed Feb 22 19:50:36 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 35666134B; Wed, 22 Feb 2006 19:50:35 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17410-01; Wed, 22 Feb 2006 19:50:29 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 9614F133F; Wed, 22 Feb 2006 19:50:26 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id BEC905ED1; Wed, 22 Feb 2006 19:50:26 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: scsh-users@scsh.net Subject: Re: SCSH status and future In-Reply-To: <20060218190712.GA13963@capsaicin.mamane.lu> References: <20060218190240.GA13741@capsaicin.mamane.lu> <20060218190712.GA13963@capsaicin.mamane.lu> X-Mailer: VM 7.19 under Emacs 20.7.1 Reply-To: Daniel Hagerty From: Daniel Hagerty Sender: Daniel Hagerty Date: Mon, 20 Feb 2006 05:55:50 +0100 (MET) Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/282 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 19:50:26 +0100 (MET) --=-=-= Content-Description: message body text > I had already removed features to work around the lack of support of > large files (64 bit C off_t type) in scsh. These features are now back > in with the switch to guile. Try the attached patch and test program. It works for me on a system with 64 bit off_t. It's not terribly tested. At a minimum, it should be validated on: * Big endian machines * Machines with 32 bit off_t (should work, but not tested). and I don't know exactly what linux does for 32 bit machines talking to large file support; I assume that's #define LARGEFILE_SUPPORT or some such, and you get a 64 bit off_t. I'm not testing this further, as I've had two computers die on me in the last 4 hours, and I'm a little fed up with planet earth. Caveats and known areas of improvement: * There's some scheme code that should be checking for bounds errors and isn't (marked XXX). This should be addressed. * I figure out the size of off_t by calling out to C for every routine that needs to know. That's strikes me as a little goofy, and should probably be detected at autoconf time and smashed into configure.scm or some such. * I didn't do anything like an exaustive search for off_t users and fix them all up; this should give you the basic idea of what to do. Hopefully this gives you something to work with. --=-=-= Content-Disposition: inline; filename=patch Content-Description: 64 bit off_t patches diff -urwB scsh-0.6.6/scsh/syscalls.scm scsh-0.6.6-largefile/scsh/syscalls.scm --- scsh-0.6.6/scsh/syscalls.scm 2003-11-12 06:07:29.000000000 -0500 +++ scsh-0.6.6-largefile/scsh/syscalls.scm 2006-02-19 23:31:04.000000000 -0500 @@ -272,9 +272,11 @@ ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ;;; STAT -(import-os-error-syscall stat-file (path data chase?) "scheme_stat") +(import-os-error-syscall stat-file (path data bytevec chase?) "scheme_stat") -(import-os-error-syscall stat-fdes (fd data) "scheme_fstat") +(import-os-error-syscall stat-fdes (fd data bytevec) "scheme_fstat") + +(import-os-error-syscall %sizeof-offt () "scsh_sizeof_offt") (define-record file-info type @@ -294,15 +296,16 @@ ;;; Should be redone to return multiple-values. (define (%file-info fd/port/fname chase?) (let ((ans-vec (make-vector 11)) + (offt-bytevec (make-byte-vector (%sizeof-offt) 0)) (file-type (lambda (type-code) (vector-ref '#(block-special char-special directory fifo regular socket symlink) type-code)))) (generic-file-op fd/port/fname (lambda (fd) - (stat-fdes fd ans-vec)) + (stat-fdes fd ans-vec offt-bytevec)) (lambda (fname) - (stat-file fname ans-vec chase?))) + (stat-file fname ans-vec offt-bytevec chase?))) (make-file-info (file-type (vector-ref ans-vec 0)) (vector-ref ans-vec 1) (vector-ref ans-vec 2) @@ -310,7 +313,7 @@ (vector-ref ans-vec 4) (vector-ref ans-vec 5) (vector-ref ans-vec 6) - (vector-ref ans-vec 7) + (byte-vector->offset (vector-ref ans-vec 7)) (vector-ref ans-vec 8) (vector-ref ans-vec 9) (vector-ref ans-vec 10)))) @@ -383,11 +384,11 @@ (error "Seek does currently not work on buffered ports" fd/port)) (let ((whence (:optional maybe-whence seek/set)) (fd (if (integer? fd/port) fd/port (port->fdes fd/port)))) - (%fd-seek fd offset whence))) + (%fd-seek fd (offset->byte-vector offset) whence))) (define (tell fd/port) (let ((fd (if (integer? fd/port) fd/port (port->fdes fd/port)))) - (%fd-seek fd 0 seek/delta))) + (%fd-seek fd (offset->byte-vector 0) seek/delta))) (import-os-error-syscall %char-ready-fdes? (fd) "char_ready_fdes") @@ -719,6 +720,41 @@ (sleazy-call/fdes fd/port (lambda (fd) (%fcntl-write fd fcntl/set-status-flags flags)))) +;;; Support routines for off_t as byte-vectors +;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; + +;; off_t might be 64 bits, which the scheme48 FFI has no native means +;; for handling. We use little endian encoded byte vectors to pass +;; the data back and forth to the FFI. +(define (offset->byte-vector offset) + (let* ((sz (%sizeof-offt)) + (vec (make-byte-vector sz 0))) + ;; XXX need to range check the offset and throw an exception if + ;; its too large for the system's off_t. + (let next-byte ((i 0)) + (if (= i sz) + vec + (let ((byte (bitwise-and + #xFF + (arithmetic-shift offset + (* -8 i))))) + (byte-vector-set! vec i byte) + (next-byte (+ i 1))))))) + +(define (byte-vector->offset bytevec) + ;; XXX validate that the bytevector is the correct size to represent + ;; an off_t and raise an error otherwise. + (let ((sz (%sizeof-offt))) + (let next-byte ((i 0) + (offset 0)) + (if (= i sz) + offset + (next-byte (+ i 1) + (+ offset + (arithmetic-shift + (byte-vector-ref bytevec i) + (* 8 i)))))))) + ;;; Miscellaneous ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; diff -urwB scsh-0.6.6/scsh/syscalls1.c scsh-0.6.6-largefile/scsh/syscalls1.c --- scsh-0.6.6/scsh/syscalls1.c 2004-03-11 10:54:06.000000000 -0500 +++ scsh-0.6.6-largefile/scsh/syscalls1.c 2006-02-19 23:13:07.000000000 -0500 @@ -555,12 +555,12 @@ */ /* Internal aux function -- loads stat values into Scheme vector: */ -s48_value really_stat(struct stat *s, s48_value vec) +s48_value really_stat(struct stat *s, s48_value vec, s48_value bytevec) { int modes, typecode = -1; - S48_DECLARE_GC_PROTECT(1); + S48_DECLARE_GC_PROTECT(2); - S48_GC_PROTECT_1(vec); + S48_GC_PROTECT_2(vec, bytevec); modes = s->st_mode; if( S_ISBLK(modes) ) typecode = 0; @@ -571,6 +571,8 @@ else if( S_ISSOCK(modes) ) typecode = 5; else if( S_ISLNK(modes) ) typecode = 6; + offt_to_bytevec(s->st_size, bytevec); + S48_VECTOR_SET(vec,0,s48_enter_fixnum(typecode)); S48_VECTOR_SET(vec,1, s48_enter_integer(s->st_dev)); S48_VECTOR_SET(vec,2, s48_enter_integer(s->st_ino)); @@ -578,7 +580,7 @@ S48_VECTOR_SET(vec,4, s48_enter_integer(s->st_nlink)); S48_VECTOR_SET(vec,5, s48_enter_integer(s->st_uid)); S48_VECTOR_SET(vec,6, s48_enter_integer(s->st_gid)); - S48_VECTOR_SET(vec,7, s48_enter_integer(s->st_size)); + S48_VECTOR_SET(vec,7, bytevec); S48_VECTOR_SET(vec,8, s48_enter_integer(s->st_atime)); S48_VECTOR_SET(vec,9, s48_enter_integer(s->st_mtime)); S48_VECTOR_SET(vec,10, s48_enter_integer(s->st_ctime)); @@ -590,7 +592,7 @@ return S48_UNSPECIFIC; } -s48_value scheme_stat(s48_value path, s48_value vec, s48_value chase_p) +s48_value scheme_stat(s48_value path, s48_value vec, s48_value bytevec, s48_value chase_p) { struct stat s; const char * cp_path = s48_extract_string(path); @@ -598,15 +600,15 @@ if (retval == -1) s48_raise_os_error_2 (errno, path, chase_p); - return really_stat (&s, vec); + return really_stat (&s, vec, bytevec); } -s48_value scheme_fstat(s48_value fd, s48_value vec) +s48_value scheme_fstat(s48_value fd, s48_value vec, s48_value bytevec) { struct stat s; int retval = fstat (s48_extract_fixnum (fd), &s); if (retval == -1) s48_raise_os_error_1 (errno, fd); - return really_stat (&s, vec); + return really_stat (&s, vec, bytevec); } s48_value scsh_symlink(s48_value sch_name1, s48_value sch_name2) @@ -706,12 +708,16 @@ s48_value sch_whence) { int retval; + off_t offset = 0; + S48_DECLARE_GC_PROTECT(3); S48_GC_PROTECT_3(sch_fdes, sch_offset, sch_whence); + offset = bytevec_to_offt(sch_offset); + retval = lseek (s48_extract_fixnum (sch_fdes), - s48_extract_integer (sch_offset), + offset, s48_extract_fixnum (sch_whence)); S48_GC_UNPROTECT(); @@ -1140,6 +1146,58 @@ return uname_record; } +/* Support for off_t expressed in byte vectors +****************** +*/ + +s48_value scsh_sizeof_offt() +{ + /* This is a goofy way of accomplishing this since off_t's size is + fixed at compile time. Make part of config.scm? */ + return(s48_enter_integer(sizeof(off_t))); +} + +/* It's expected that sch_bytevec is already gc protected */ +off_t bytevec_to_offt(s48_value sch_bytevec) { + char *bytevec; + int i; + const size_t sz = sizeof(off_t); + off_t retval = 0; + + if(S48_BYTE_VECTOR_LENGTH(sch_bytevec) != sz) + /* From my reading, raising an exception doesn't need to call + GC_UNPROTECT functions. This is based on the extract functions + raising errors without doign so. */ + s48_raise_argument_type_error(sch_bytevec); + + bytevec = s48_extract_byte_vector(sch_bytevec); + + /* This implies a little endian encoding */ + for(i = 0; i < sz; i++) { + retval |= ((off_t)bytevec[i]) << (i * 8); +#if 0 + printf("0x%016qx, %02x, %d, %d\n", retval, bytevec[i], i, (i * 8)); +#endif + } + + return(retval); +} + +/* It is expected that sch_bytevec is already gc protected */ +void offt_to_bytevec(off_t offset, s48_value sch_bytevec) { + const int sz = sizeof(off_t); + char *bytevec; + int i; + + if(S48_BYTE_VECTOR_LENGTH(sch_bytevec) != sz) + s48_raise_argument_type_error(sch_bytevec); + + bytevec = s48_extract_byte_vector(sch_bytevec); + + for(i = 0; i < sz; i++) + bytevec[i] = (offset >> (8 * i)) & 0xff; +} + void s48_init_syscalls (){ S48_EXPORT_FUNCTION(scheme_exec); S48_EXPORT_FUNCTION(scsh_exit); @@ -1206,6 +1264,9 @@ S48_EXPORT_FUNCTION(errno_msg); S48_EXPORT_FUNCTION(scm_crypt); S48_EXPORT_FUNCTION(scm_uname); + + S48_EXPORT_FUNCTION(scsh_sizeof_offt); + S48_GC_PROTECT_GLOBAL(envvec_record_type_binding); S48_GC_PROTECT_GLOBAL(add_envvec_finalizerB_binding); S48_GC_PROTECT_GLOBAL(current_env); diff -urwB scsh-0.6.6/scsh/syscalls1.h scsh-0.6.6-largefile/scsh/syscalls1.h --- scsh-0.6.6/scsh/syscalls1.h 2001-09-07 12:05:31.000000000 -0400 +++ scsh-0.6.6-largefile/scsh/syscalls1.h 2006-02-19 22:44:37.000000000 -0500 @@ -87,9 +87,9 @@ int write_stream_substring(s48_value buf, int start, int end, FILE *f); -s48_value scheme_stat(s48_value path, s48_value vec, s48_value chase_p); +s48_value scheme_stat(s48_value path, s48_value vec, s48_value bytevec, s48_value chase_p); -s48_value scheme_fstat(s48_value fd, s48_value vec); +s48_value scheme_fstat(s48_value fd, s48_value vec, s48_value bytevec); s48_value scsh_getgid(); @@ -146,3 +146,9 @@ s48_value scm_closelog(); s48_value sleep_until(); + +/* New support for off_t greater than 32 bits. Use bytevecs */ +s48_value scsh_sizeof_offt(); + +off_t bytevec_to_offt(s48_value sch_bytevec); +void offt_to_bytevec(off_t offset, s48_value sch_bytevec); --=-=-= Content-Disposition: inline; filename=tst.scm Content-Description: test program (define file-name "tstfile") (define file (open-output-file file-name)) (set-port-buffering file bufpol/none) (define bigfile-seek (* 8 1024 1024 1024)) (define test-string "flobby") (define bigfile-size (+ bigfile-seek (string-length test-string))) (seek file bigfile-seek seek/set) (write-string test-string file) (close file) (define actual-size (file-info:size (file-info file-name))) (format (current-output-port) "Expected ~a Actual ~a" bigfile-size actual-size) (newline) (format (current-output-port) "Matches? ~a" (= bigfile-size actual-size)) (newline) --=-=-=-- From scsh-users-request@scsh.net Wed Feb 22 20:05:37 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 4918112B; Wed, 22 Feb 2006 20:05:34 +0100 (NFT) Received: from mx1.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx1 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36450-03; Wed, 22 Feb 2006 20:05:29 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx1.informatik.uni-tuebingen.de (Postfix) with ESMTP id 2B8F5110; Wed, 22 Feb 2006 20:05:26 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 12D735ECF; Wed, 22 Feb 2006 20:05:25 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net To: George Demmy Cc: scsh-users@scsh.net Subject: Re: patch for io.c: scsh won't build with gcc 4.0.2 References: From: Martin Gasbichler Date: Wed, 22 Feb 2006 20:05:13 +0100 In-Reply-To: (George Demmy's message of "Mon, 20 Feb 2006 11:50:37 -0500") Message-ID: User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/283 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Wed, 22 Feb 2006 20:05:25 +0100 (MET) George Demmy writes: > I've been playing with scsh since the early 0.5 days, so imagine my > surprise when a routine configure; make ; make install for 0.6.6 blew > up on a Fedora 4 box. The problem is with c/unix/io.c. gcc 4.0.2 > doesn't like the storage class specification for the declaration of > write_integer in ps_write_integer (and I don't blame it). Also, it's > freaking out about type mismatches arisiing from mixed use of singed > and unsigned longs. I've checked the CVS sources out, and get the same > problem. I've included a patch that fixes the problem. You've probably fetched the HEAD which is not up-to-date at the moment: the few fixes we added recently (including support for gcc 4.0) were applied to the r0-6-stable branch only. Sorry, I'll sync the changes back as soon as 0.6.7 has been released. -- Martin From scsh-users-request@scsh.net Thu Feb 23 09:52:05 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id EE92912F3; Thu, 23 Feb 2006 09:52:01 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31356-01; Thu, 23 Feb 2006 09:51:58 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id A327F12E1; Thu, 23 Feb 2006 09:51:56 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id CADE15ED1; Thu, 23 Feb 2006 09:51:54 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: Immanuel Normann User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: de-DE, de, en-us, en To: scsh-users@scsh.net Subject: looking for sxml-tools for scsh Sender: immanuel.normann@web.de Date: Thu, 23 Feb 2006 01:49:49 +0100 (MET) Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Resent-Message-ID: <9GPnhB.A.tfC.peX_DB@bernard> Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/284 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Thu, 23 Feb 2006 09:51:54 +0100 (MET) has anybody tried succefully to adjust (and package) Kirill Lisovsky's sxml-tools for scsh? (http://www196.pair.com/lisovsky/xml/sxmltools/) That would be nice! Or are there other compairable libs for scsh around? In particular I am looking for the inverse of ssax:xml->sxml i.e. a function ssax:sxml->xml. (I don't understand why it is not part of the SSAX libray. Sure ssax:sxml->xml is trivial compaired with ssax:xml->sxml (may be too trivial for the SSAX lib) and in fact I have already implemented it once in Lisp. And maybe many of these helpful functions in sxml-tools are more or less straightforward to implement. But reinventing the wheel is frustrating.) Thanks for any hint, Immanuel From scsh-users-request@scsh.net Fri Feb 24 01:07:19 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id D170812DF; Fri, 24 Feb 2006 01:07:17 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19448-05; Fri, 24 Feb 2006 01:07:15 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 4C63A1223; Fri, 24 Feb 2006 01:07:14 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 361B35ED3; Fri, 24 Feb 2006 01:07:13 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: scsh-users@scsh.net From: RT Happe Subject: Re: looking for sxml-tools for scsh Date: Fri, 24 Feb 2006 01:06:37 +0100 To: Immanuel Normann X-Mailer: Apple Mail (2.623) Sender: rthappe@web.de X-Sender: rthappe@web.de Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/285 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Fri, 24 Feb 2006 01:07:13 +0100 (MET) Immanuel Normann wrote: > In particular I am looking for the inverse of ssax:xml->sxml i.e. a > function ssax:sxml->xml. You're probably aware of SXML->HTML in SSAX/scheme/SXML-to-HTML.scm, not quite what you ask for but fairly close. rthappe From scsh-users-request@scsh.net Fri Feb 24 08:08:13 2006 Return-Path: X-Original-To: scsh@informatik.uni-tuebingen.de Delivered-To: scsh@informatik.uni-tuebingen.de Received: from localhost (loopback [127.0.0.1]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id AD6CB137E; Fri, 24 Feb 2006 08:08:10 +0100 (NFT) Received: from mx4.informatik.uni-tuebingen.de ([127.0.0.1]) by localhost (mx4 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19216-03; Fri, 24 Feb 2006 08:08:04 +0100 (NFT) Received: from www.scsh.net (bernard.Informatik.Uni-Tuebingen.De [134.2.12.122]) by mx4.informatik.uni-tuebingen.de (Postfix) with ESMTP id 310E8138A; Fri, 24 Feb 2006 08:07:30 +0100 (NFT) Received: by www.scsh.net (Postfix, from userid 3123) id 090915ED3; Fri, 24 Feb 2006 08:07:29 +0100 (MET) Old-Return-Path: X-Original-To: scsh-users@scsh.net Delivered-To: scsh-users@scsh.net From: Michael Sperber To: Immanuel Normann Cc: scsh-users@scsh.net Subject: Re: looking for sxml-tools for scsh References: Date: Fri, 24 Feb 2006 08:07:15 +0100 In-Reply-To: (Immanuel Normann's message of "Thu, 23 Feb 2006 01:49:49 +0100 (MET)") Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.5-b24 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Virus-Scanned: ClamAV using ClamSMTP Content-Transfer-Encoding: quoted-printable Resent-Message-ID: Resent-From: scsh-users@scsh.net X-Mailing-List: archive/latest/286 X-Loop: scsh-users@scsh.net List-Post: List-Help: List-Subscribe: List-Unsubscribe: Precedence: list Resent-Sender: scsh-users-request@scsh.net List-Id: List-Archive: Resent-Date: Fri, 24 Feb 2006 08:07:29 +0100 (MET) Immanuel Normann writes: > has anybody tried succefully to adjust (and package) Kirill Lisovsky's=20 > sxml-tools for scsh? > (http://www196.pair.com/lisovsky/xml/sxmltools/) Yes. (Or at least for Scheme 48. Remaining adjustments should be trivia= l.) But this was a few months ago---the package may have moved on, and I couldn't find an arrangement with Kirill that would allow me to maintain it effectively. I'd be happy to send you what I have (and even happier if you would take over maintaining it)---it should at least significantly reduce the work needed to get you started. Just let me know. --=20 Cheers =3D8-} Mike Friede, V=F6lkerverst=E4ndigung und =FCberhaupt blabla