Stephen Paul Weber wrote on Tuesday, April 21, 2009 9:59 AM:
> On Tue, Apr 21, 2009 at 06:50, Buchbinder, Barry (NIH/NIAID) [E]
> 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 /c
Stephen Paul Weber wrote:
> 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
On Tue, Apr 21, 2009 at 06:50, Buchbinder, Barry (NIH/NIAID) [E]
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 t
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 creat
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
obv
5 matches
Mail list logo
