> Why not allow (and generate with mkgroup) URL encoding e.g.
> "Domain%20Users"?
Good idea that'd hopefully work, too!
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://c
On Mon, Jun 11, 2012 at 1:26 PM, Andrew DeFaria wrote:
> On 6/11/2012 9:25 AM, Eric Blake wrote:
>>>
>>> Perhaps CYGWIN could have used a tab to separate the group names?
>>
>> What's to say that 'TAB' won't be valid in a group name?
>
> What's to say that any characters won't be valid in a nam
On 6/11/2012 9:25 AM, Eric Blake wrote:
Perhaps CYGWIN could have used a tab to separate the group names?
What's to say that 'TAB' won't be valid in a group name?
What's to say that any characters won't be valid in a name? Nothing. You
gotta pick something and start somewhere..
--
Andrew
On 06/11/2012 10:13 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
> 2. Since Windows group names can embed spaces, the output of the "groups"
> shell command
'groups' is no longer a shell command, but an executable, for several
coreutils releases now.
>is unparsable in CYGWIN (scripting b
Hi,
I have been porting quite a bit of software from native UNIX environment to
CYGWIN,
and despite there is a very elaborate UNIX group handling/mapping in CYGWIN,
there
are still a few discrepancies I would like to note:
1. When a user is a member of multiple Windows groups, this fact is not
5 matches
Mail list logo