Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: From: Mellman Thomas To: "'cygwin AT cygwin DOT com'" Subject: RE: A proposal for a Cygnus naming convention Date: Wed, 8 May 2002 17:05:51 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" >>-----Original Message----- >>From: Gilgamesh Nootebos [mailto:Gilgamesh DOT Nootebos AT elegant DOT nl] >>Sent: Wednesday, May 08, 2002 4:56 PM >>To: cygwin AT cygwin DOT com >>Subject: Re: A proposal for a Cygnus naming convention >> >> >>Mellman Thomas wrote: >>> >>> Okay, it's clear now that it won't be possible to keep >>things easy to parse. >>> >>This is almost trivially easy if I wanted to manipulate >>mounts points in >>a script: >> >>$ regtool -k list 'HKLM\software\Cygnus Solutions\Cygwin\mounts v2' >> >/ >> >/usr/bin >> >/usr/lib >> >/home >> >>$ regtool get 'HKLM\software\Cygnus Solutions\Cygwin\mounts >>v2\/home\native' >> >C:\Documents and Settings\gilgames\Mijn Documenten >> >>There is only one reason I might want to do this; with >>mount(1) I can't >>easily get exactly the string I want without falling back to >>something >>like sed/awk/perl/. >> >>And unices handle [[:space:]] characters very well, but it just isn't >>tradition to use them. It's just that I like to use split() in perl or $1, $2, $3 in awk. To say it's "easy" to handle blanks with Unix is ... well, to avoid anything that might inflame, let's say, academic. Incidently, I haven't heard anyone explain what purpose the blank in "mount v2" serves. -- 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/