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 Date: Tue, 7 May 2002 11:19:29 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: A proposal for a Cygnus naming convention Message-ID: <20020507151929.GE8362@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23.1i On Tue, May 07, 2002 at 09:32:00AM +0200, Mellman Thomas wrote: >Given the registry name: > > >HKLM\software\Cygnus solutions\cygwin\mounts v2\/ > > >May I suggest that the blank in the name is superfluous and problematic >for processing by Unix-type tools - even in the registry. Bill may >feel vindicated that *his* OS tolerates blanks, but does it really add >significant readibility? You can suggest anything, however, what you are suggesting makes no sense: 1) The cygwin registry entry is not intended to be manipulated by "Unix-type tools". Use *mount* if you want to manipulate it. 2) Changing the name would break backwards compatibility. 3) Even if you wanted to use "Unix-type" tools, a space is really not an obstacle. Unix certainly can deal with spaces. So, bottom line is that there is absolutely no way that we'll be changing anything. You should just be considering the registry to be a black box, anyway. The cygwin DLL deals just fine with the current scheme. cgf -- 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/