Re: Using real paths in ash

[Stephen Paul Weber <singpolyma at singpolyma dot net>]

On Tue, Apr 21, 2009 at 06:50, Buchbinder, Barry (NIH/NIAID) [E]
<BBuchbinder@niaid.nih.gov> wrote:
> Stephen Paul Weber wrote on Tuesday, April 21, 2009 9:39 AM:
>> I really like the cygwin ash.exe, but I have a problem. ÂIt tries to
>> replace C: with /cygdrive/c everywhere. ÂThis actually breaks my
>> utilities, because they expect real Windows paths. Âmkdir -p
>> "$TEMP/t" for example ends up creating
>> C:\cygdrive\c\DOCUME~1\NEWUSE~1\LOCALS~1\Temp\t Â... which is
>> obviously not what I want.
>
> man cygpath
>
> Don't forget quotes, e.g.
>
> $ mkdir -p "$(cygpath -u "${TEMP}/t")"

Ok, I'm aware of cygpath, but the question was how can I actually fix
the problem.  See, I want to use it as a shell script interpreter on
Windows, and if I throw cygpath calls all over my shell scripts, then
they won't run on UNIX anymore.

I've been poking at the ash and pdksh code to see if I can figure out
at what point this broken behaviour gets introduced, but so far no
luck with finding it or with compiling either of them.

-- 
Stephen Paul Weber, @singpolyma
Please see <http://singpolyma.net> for how I prefer to be contacted.
This message was sent from the GMail webmail interface. It's probably
not signed.  This is a problem.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/