From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-34324-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 20144 invoked by alias); 19 Jan 2015 10:40:11 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 34324
Received: (qmail 17345 invoked from network); 19 Jan 2015 10:39:59 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7fc86d0000066b7-0a-54bcdefd2850
Date: Mon, 19 Jan 2015 10:39:53 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Command substitution parsing issues (not really Re: completion)
Message-id: <20150119103953.440441b7@pwslap01u.europe.root.pri>
In-reply-to: <20150119102910.18102a0b@pwslap01u.europe.root.pri>
References: <54B9AA99.6080403@eastlink.ca>
 <150116185732.ZM30791@torch.brasslantern.com> <54B9D726.2020108@eastlink.ca>
 <20150119102910.18102a0b@pwslap01u.europe.root.pri>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsVy+t/xa7p/7+0JMTjUYW5xsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mnpmn2QqeM1RsaHrF1sD4y+2LkZODgkBE4mpV/8zQthiEhfu
	rQeKc3EICSxllLjatJMVwlnCJLFsyhZmCGcbo8SjVd+AHA4OFgFViftrAkG62QQMJaZumg02
	SURAXOLs2vMsILawgI/E4f1fwGxeAXuJ2RN72UFsTgEHidaTZxkhZq5nlNjdPo8VJMEvoC9x
	9e8nJoiT7CVmXjnDCNEsKPFj8j2wQcwCWhKbtzWxQtjyEpvXvGUGsYUE1CVu3N3NPoFRaBaS
	lllIWmYhaVnAyLyKUTS1NLmgOCk910ivODG3uDQvXS85P3cTIyRsv+5gXHrM6hCjAAejEg9v
	RNbuECHWxLLiytxDjBIczEoivIwX9oQI8aYkVlalFuXHF5XmpBYfYmTi4JRqYHS4kb9o1uv9
	qwVM9SwtT7FEhf0OKNl90ZF1y7Ib0+Z8V4qaZ6Th9W69yOopUhuuHPvDeGaqW1jnL8vvDuYZ
	H1j9wrlLlup49ohP1eibxu3ZKKkWNDW/88j9eGn2iIKUHaxfmQ54F/DlnulU3XvixlLvDnPz
	uoN123jq3RN79as8Em8fXptzQomlOCPRUIu5qDgRAPMbXSE5AgAA

On Mon, 19 Jan 2015 10:29:10 +0000
Peter Stephenson <p.stephenson@samsung.com> wrote:
> On Fri, 16 Jan 2015 19:29:42 -0800
> Ray Andrews <rayandrews@eastlink.ca> wrote:
> > > In fact if you're going to live on the bleeding edge of git pull, you
> > > should have a separate shared-object directory for every build.
> > 
> > Can you suggest a method?
>
> I find it good enough to be able to point the compiled executable in Src
> at a special set of libraries by using an environment variable (you
> could even avoid that if you detected where the shell was running from
> early enough).>
>
> The basic idea (the actual implementation has got complicated) is
> .zshenv contains
>
> if [[ -n $TEST_MODULES ]]; then
>   module_path=(~/src/zsh/modules .)
> fi
>
> and the module links were set up with some variant of the function
> below.

...and I see I haven't even bothered to explain the main point of this:
the module directory just contains links back into the compilation tree.
So you only ever do this once; after that you just remember to use

TEST_MODULES=1 ./zsh

when running in Src.

pws