From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104645 invoked by alias); 21 Nov 2016 12:52:57 -0000 Mailing-List: contact kawa-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: kawa-owner@sourceware.org Received: (qmail 104629 invoked by uid 89); 21 Nov 2016 12:52:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.7 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=locates, snow, Snow, H*x:1.6 X-HELO: homiemail-a20.g.dreamhost.com Received: from sub3.mail.dreamhost.com (HELO homiemail-a20.g.dreamhost.com) (69.163.253.7) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 21 Nov 2016 12:52:45 +0000 Received: from homiemail-a20.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a20.g.dreamhost.com (Postfix) with ESMTP id 3FE7D7EC069 for ; Mon, 21 Nov 2016 04:52:44 -0800 (PST) Received: from vereq.eip10.org (cpe-74-75-122-130.maine.res.rr.com [74.75.122.130]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: chaw@eip10.org) by homiemail-a20.g.dreamhost.com (Postfix) with ESMTPSA id 226717EC064 for ; Mon, 21 Nov 2016 04:52:44 -0800 (PST) Received: from chaw by vereq.eip10.org with local (Exim 4.84_2) (envelope-from ) id 1c8o5T-0003D7-3I for kawa@sourceware.org; Mon, 21 Nov 2016 07:52:43 -0500 To: kawa Subject: kawa.include.path and "|"; library setup recommendations? From: "Sudarshan S Chawathe" Reply-To: "Sudarshan S Chawathe" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12343.1479732763.1@vereq.eip10.org> Date: Mon, 21 Nov 2016 12:52:00 -0000 Message-ID: <12344.1479732763@vereq.eip10.org> X-IsSubscribed: yes X-SW-Source: 2016-q4/txt/msg00070.txt.bz2 Summary: Q1. How is "|" in kawa.include.path interpreted in the case of nested includes? Q2. Any recommendations for setting up local libraries for Kawa? Details: I have a question that I think is about the semantics of "|" in kawa.include.path. Briefly, in the case of nested includes, does the "|" refer to the directory of the original (top level) file or the directory of the most recent including file? I thought it would refer to the most recent (innermost) including file, but I suspect I am wrong (or something is messed up in my setup). For example, suppose I have set kawa.include.path to "|:/a/b" and the following files exist: /a/b/c/d.sld /a/b/c/e.scm I have a top-level file work.scm (in working directory /p/q, say) which has the form (include "c/d.sld") in it. Further, the file d.sld has (include "e.scm") in it. I have found that Kawa locates d.sld as expected but complains about not being able to locate e.scm. Adding the directory /a/b/c to kawa.include.path solves the problem. My more general, and bit more vague, question is: What is a recommended method for setting up libraries locally for Kawa? Background: I'm trying to set up a local directory structure that will make it easy to import libraries into Kawa. Currently, I'm using some material from snow-fort.org, some from the TaylanUB/scheme-srfis collection from GitHub, and some minor home-grown code. I'd like to just be able to unpack the files in a directory or two and then have (include "foo/bar.sld") and the like work without having to modify include paths. (I realize Snow has a solution to a very similar problem, but I think I'd need something else for non-Snow code anyway.) Regards, -chaw