Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: paths like //usr/local References: <20021015181721.GB11463@redhat.com> <20021015194810.GA14116@redhat.com> Organization: Jan at Appel Mail-Followup-To: cygwin@cygwin.com From: Jan Nieuwenhuizen Date: Tue, 15 Oct 2002 22:00:56 +0200 In-Reply-To: <20021015194810.GA14116@redhat.com> (Christopher Faylor's message of "Tue, 15 Oct 2002 15:48:10 -0400") Message-ID: <87r8ero4jr.fsf@peder.flower> Lines: 21 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) Emacs/21.2 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Christopher Faylor writes: > cygwin allows the user to specify paths like: c:\foo\bar and c:/foo/bar. > Similarly, it allows //foo/bar and \\foo\bar . > If that doesn't satisfy you then you can go back to the "Because we're mean" > argument. I've been hurt by this too, and it makes me think. It would be even more satisfactory if some configurable list of 'hosts' would map to //localhost/. Hosts with names such as \\bin, \\etc, \\tmp, \\usr or \\var come to mind. Now if such a thing could be implemented without some horrible kludge, would that be nice? Jan. -- Jan Nieuwenhuizen | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org -- 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/