From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26579 invoked by alias); 10 Apr 2014 18:39:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 26565 invoked by uid 89); 10 Apr 2014 18:39:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: etr-usa.com Received: from etr-usa.com (HELO etr-usa.com) (130.94.180.135) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 Apr 2014 18:39:28 +0000 Received: (qmail 11435 invoked by uid 13447); 10 Apr 2014 18:39:26 -0000 Received: from unknown (HELO [172.20.0.42]) ([68.35.121.157]) (envelope-sender ) by 130.94.180.135 (qmail-ldap-1.03) with SMTP for ; 10 Apr 2014 18:39:26 -0000 Message-ID: <5346E55D.6020405@etr-usa.com> Date: Thu, 10 Apr 2014 18:39:00 -0000 From: Warren Young User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Still testing needed: New passwd/group AD/SAM integration References: <20140410145323.GB2437@calimero.vinschen.de> <5346B667.3040704@breisch.org> <20140410152809.GD2437@calimero.vinschen.de> In-Reply-To: <20140410152809.GD2437@calimero.vinschen.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-04/txt/msg00264.txt.bz2 On 4/10/2014 09:28, Corinna Vinschen wrote: > > The only reason I dislike backslash a bit is, that the backslash is > the escape char in the shell, so you would have remember every time > you type in such an account name to escape the account name, > DOMAIN\\username or "DOMAIN\username" Is this DOMAIN\username syntax merely mimicking a Windowsism, or does it directly translate into a semantically meaningful construct to Windows? I mean, do you have to parse it and reassemble the data for Windows' benefit, or do you pass this string straight to some Windows API? If cygwin1.dll must premasticate the string for Windows' benefit, you can use any separator character you like. In that case, I'd think forward slash makes more sense, since it says, "This works like POSIX paths: cygwin1.dll is translating this to something else for you behind the scenes." Backslash signals that what you're doing is something Windows understands natively. As for your original question, I can't see why you'd need it to be configurable as long as it's escapable. If you can escape the delimiter, then you can hardcode it to anything you like, since there's a path out of any conflict. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple