Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <3BA68215.8010004@likai.net>
Date: Mon, 17 Sep 2001 19:07:01 -0400
From: Li-Kai Liu <news AT likai DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20010913
X-Accept-Language: en-us
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: using aliases for cygwin commands on win2k
References: <20010917225406 DOT 95591 DOT qmail AT web11106 DOT mail DOT yahoo DOT com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

>
>
>
>Thanks for the response.
>
>If I do that, I lose the ability to start applications
>automatically by simply typing the file name.  For example, 
>if I have a file try.doc, and I type try.doc at the Windows 
>2000 command prompt, it brings up Word with that document.
>
>-Anoop
>
you might consider using batch files to wrap around the commands that 
you want to alias, and put the batch files to wherever %PATH% can find.

sample batch file for alias dir='ls -l'

---- dir.bat starts here ----
@ls.exe -l %1 %2 %3 %4 %5 %6 %7 %8 %9
---- dir.bat ends here ----

or something like that. that's the best I can do with cmd.exe

liulk

just something i suddenly remembered ... when i was little (say 11 or 
something), i used to have fear on .exe files (in MS-DOS) because they 
have MZ headers and relocation table. just something i remembered ... ;-)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/