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: <3CD93C6E.7080807@elegant.nl> Date: Wed, 08 May 2002 16:55:42 +0200 From: Gilgamesh Nootebos Reply-To: cygwin AT cygwin DOT com Organization: The Elegant Group User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0rc1) Gecko/20020417 X-Accept-Language: nl, en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: A proposal for a Cygnus naming convention References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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. gilgames -- Gilgamesh Nootebos (Elegant Relational Development) @: Gilgamesh DOT Nootebos AT elegant DOT nl T: +31 36 54 77 100 -- 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/