This is the mail archive of the
mailing list for the Cygwin project.
Re: example needed pls: `cygpath -c <HANDLE>'
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 01 Jul 2003 05:31:51 -0700
- Subject: Re: example needed pls: `cygpath -c <HANDLE>'
- Organization: My own little world...
- References: <Xns93A88A37D41F9soren1Gmane@18.104.22.168> <3EFDDF97.29F49125@dessent.net> <Xns93A896696C0F8soren1Gmane@22.214.171.124> <20030701035345.GC7604@ny-kenton2a-710.buf.adelphia.net>
Soren Andersen wrote:
> In short although I see what you are doing, I think it's too simple for
> many cases and its lack of robustness makes it only marginally useful to
> me (IMHO). If you could post some typical examples of how you use it, to
> refute me, I'd be pleased.
Yes, it's quite dumb code. It doesn't even work correctly if one of the
files doesn't exist. However it works perfectly for what I originally
devised it for, which is using Windows editors from cygwin, as in I have
alias ue="dodos /path/to/uedit32.exe $@"
in .profile, and so I can issue commands like "ue /etc/hosts*" or "ue
~/project/foo*.c" to edit files with UltraEdit as if it was a
cygwin-aware application. Surely it will choke on arguments and almost
anything else except globs referring to existing files.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html