X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Anqa7jL+Q0M5U7KfuBLaA4ScNx/l1Kfu6Kjrv0AkGW3
	e4Tv9koPcLMqGnYn8SKW7Nf3uXjGxNjSpDIq5mC/j04YVAgYYJEFxkgnVJc73Dt5
	5M/5shbyvQyZVWnTQSoSu0Ds1N5o66GM24xN2avSNbdoeBvFyW4A9xwiC/UDxZ2Y
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=BoveSzU7OkIwGuKpD0R3AS98Hsg=; b=wG/rjpGgdgyttnYTg
	GMOUUw9C9c26en5506It+WU3emCl52DCJVZMY4BBn/Xt12SyeZk1QKd2JYmNndUE
	dI/642ACqrfQKlBhV0U33GTpWpoAsJ91ppeMY7S1+dlaYNTlYMqoMJkq8EiuaWZd
	GC2/bvkBGTmAr6B3H7NLTf7hI0=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
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
Message-ID: <5346E55D.6020405@etr-usa.com>
Date: Thu, 10 Apr 2014 12:39:25 -0600
From: Warren Young <warren AT etr-usa DOT com>
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 AT cygwin DOT com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
References: <20140410145323 DOT GB2437 AT calimero DOT vinschen DOT de> <5346B667 DOT 3040704 AT breisch DOT org> <20140410152809 DOT GD2437 AT calimero DOT vinschen DOT 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

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