Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: cygwin AT cygwin DOT com
From: Soren A <somian AT adelphia DOT net>
Subject: Re: example needed pls: `cygpath -c <HANDLE>'
Date: Wed, 2 Jul 2003 19:03:58 +0000 (UTC)
Organization: Occasionally Sporadically
Lines: 35
Message-ID: <Xns93AC99597E004soren1Gmane@80.91.224.249>
References: <3EFE120B DOT 58A0C79E AT dessent DOT net> <Pine DOT GSO DOT 4 DOT 44 DOT 0306282234360 DOT 22307-100000 AT slinky DOT cs DOT nyu DOT edu> <20030701040434 DOT GE7604 AT ny-kenton2a-710 DOT buf DOT adelphia DOT net> <3F018740 DOT B28F53DC AT dessent DOT net> <3F018D6C DOT EA1226CA AT dessent DOT net> <Xns93ABB16F2D760soren1Gmane AT 80 DOT 91 DOT 224 DOT 249> <3F021C46 DOT C8F4CE31 AT dessent DOT net> <Xns93AC469331861soren1Gmane AT 80 DOT 91 DOT 224 DOT 249> <Xns93AC47EC6AA77soren1Gmane AT 80 DOT 91 DOT 224 DOT 249> <3F02DA32 DOT EAD1FC18 AT dessent DOT net>
X-Complaints-To: usenet AT main DOT gmane DOT org
User-Agent: Xnews/L5
X-Archive: encrypt

Brian Dessent <brian AT dessent DOT net> wrote around 02 Jul 2003 
news:3F02DA32 DOT EAD1FC18 AT dessent DOT net:

> I agree that REG_EXPAND_SZ is "nicer" in terms of not hard-coding
> paths, but since $CYGROOT is non-standard I don't see that it matters
> too much.

Yes <giggle>. (Finding this so much fun, there's nothing like throwing
megatons of programming technique at a tiny little problem that several
readers are no doubt snickering at ...). 

So, next escalation is to either write a dialogue (either in the C version 
or sticking to scripting, maybe cook up a .WSH script). If doing the 
scripting version, we'll have Perl do some heuristics, first checking for 
%CYGROOT% and accepting whatever that is, IF it is defined, and next, 
looking in the "standard" (M$-speak: "well known") place (C:\Cygwin), and 
if that fails write code to find a Cygwin key in the Registry and pull the 
install location out of that. OR we could just tell users that they must 
execute it in the CYGROOT (top of Cygwin location), and find a way to put 
the cwd into the .REG entries before executing.

Now that I think of it, the latter is the most sensible notion, if we were 
sticking to scripting. But I like the C version which is far superior.

Anybody know how to put a little Cygwin icon next to the context-menu 
entries where "SFN CygPath" and "LFN CygPath" appear? ;-)  (this is most 
likely an OLE / COM thing and far more work than it's worth... ?)

More later...

-- 
"So, tell me, my little one-eyed one, on what poor, pitiful,
defenseless planet has my MONSTROSITY been unleashed?"
                       - Dr. Jumba, Disney's "Lilo & Stitch"
OpenPGP Key at http://savannah.gnu.org/people/viewgpg.php?user_id=6050


--
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/