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 becomes problematic), because the space > is used both > in the group names (as obtained from Windows) and to delimit the group > names in the groups' > output: Such a proposal should be made to upstream coreutils, as it could possibly be of benefit to more platforms than just cygwin. > 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? > Or list each group on an individual line? An option to request alternative output format (whether that be line-separated, or even NUL-byte separated) might indeed be more palatable. -- Eric Blake ebl...@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
