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 Reply-To: Cygwin List Message-Id: <6.1.0.6.0.20040904132407.034d4430@pop.prospeed.net> X-Sender: Date: Sat, 04 Sep 2004 13:32:12 -0400 To: linda w , cygwin@cygwin.com From: Larry Hall Subject: Re: /proc registry access In-Reply-To: <41390426.7070100@tlinx.org> References: <413831C5.6010803@tlinx.org> <41390426.7070100@tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 07:54 PM 9/3/2004, you wrote: >Igor Pechtchanski wrote: > >>Yes. Cygwin will not process paths that contain a ":" -- perhaps >> >>erroneously, as it should probably check that the ":" is the second >>character, preceded by a letter. . >> >--- > Do you think it would be desirable to have cygwin not encumber itself >with character/filename validity, but instead let it be processed by the >underlying subsystem (or pseudo subsystem, in this case). Thanks for >the MLADP. What pseudo subsystem is that? Win32? Cygwin does what it does to support POSIX path semantics while still providing reasonable support for Win32 path semantics. But like Igor said, if you have an idea to improve the handling, . Having a concrete patch always focuses the discussion very quickly. :-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/