From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <25855-1274326837-4010@sneakemail.com>
References: <AANLkTimRCs5NIOrs4yPPwzDHsdFXypMHidvRfQYT4luv@mail.gmail.com>
	<AANLkTimvaWeFiRd-DfJtXc9S2daZ0PBvVxzySID4Ztlo@mail.gmail.com>
	<25855-1274326837-4010@sneakemail.com>
Date: Thu, 20 May 2010 11:20:23 +0530
Message-ID: <AANLkTim2nYfzgItYG8AXKsDITT2ntcqay3-Y9icNcER6@mail.gmail.com>
From: Arvindh Rajesh Tamilmani <arvindht@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] Acme-sac integration with Windows NT
Topicbox-Message-UUID: 287b334a-ead6-11e9-9d60-3106f5b1d025

> How do you folks using acme-sac on Windows deal with the line-ending
> issue?

pipefs(4) can be used to filter windows directory trees:
http://groups.google.com/group/acme-sac/msg/973e8c67b33a7976

and also to filter /chan/snarf (in $home/lib/profile):
http://groups.google.com/group/acme-sac/msg/cf5b3107e0d00d49

os commands can be filtered through dcr:
http://code.google.com/p/acme-sac/source/browse/man/1/dcr
for an example, see the ant wrapper i posted in this thread.

/n/sources/rsc/contrib/scripts:
http://groups.google.com/group/acme-sac/msg/15378eee84e15052

arvindh