public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Still testing needed: New passwd/group AD/SAM integration
Date: Fri, 11 Apr 2014 12:22:00 -0000	[thread overview]
Message-ID: <20140411122240.GD23281@calimero.vinschen.de> (raw)
In-Reply-To: <53471980.4090406@etr-usa.com>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On Apr 10 16:21, Warren Young wrote:
> On 4/10/2014 14:20, Eric Blake wrote:
> >is BOUND to go wrong.  The expression
> >
> >~a/b/file
> >
> >is NOT requesting 'file' within user 'a/b's home, but 'b/file' within
> >user 'a's home.
> 
> Excellent point.
> 
> Doesn't that also argue against backslash, due to the DLL's attempts
> to automatically cope with DOS paths?
> 
> Once you exclude all characters that neither the shell nor the DLL
> nor Windows will interpret specially, what's left?  According to
> TLDP[*], nothing.
> 
> Soooo....emoji?  :)

Or Non-breaking-space...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-04-11 12:22 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-10 14:53 Corinna Vinschen
2014-04-10 15:19 ` Chris J. Breisch
2014-04-10 15:28   ` Corinna Vinschen
2014-04-10 18:39     ` Warren Young
2014-04-10 19:04       ` Corinna Vinschen
2014-04-10 20:21         ` Larry Hall (Cygwin)
2014-04-10 21:13         ` Eric Blake
2014-04-10 22:22           ` Warren Young
2014-04-11 12:22             ` Corinna Vinschen [this message]
2014-04-11 12:19           ` Corinna Vinschen
2014-04-13 10:35             ` Andrey Repin
2014-04-14  8:08               ` Corinna Vinschen
2014-04-14  9:05                 ` Andrey Repin
2014-04-13 10:35           ` Andrey Repin
2014-04-14  8:21             ` Corinna Vinschen
2014-04-10 17:21 ` Ken Brown
2014-04-10 17:49   ` Corinna Vinschen
2014-04-13 10:50     ` Andrey Repin
2014-04-14  8:24       ` Corinna Vinschen
2014-04-10 18:42 ` Warren Young
2014-04-10 19:11   ` Corinna Vinschen
2014-04-10 19:16     ` Corinna Vinschen
2014-04-11  2:17     ` Duncan Roe
2014-04-11  3:47       ` Warren Young
2014-04-11  6:20         ` Duncan Roe
2014-04-11 12:39           ` Corinna Vinschen
2014-04-12  0:06             ` Duncan Roe
2014-04-10 19:46 ` Achim Gratz
2014-04-10 20:24   ` Eric Blake
2014-04-11 12:45     ` Corinna Vinschen
2014-04-11 12:43   ` Corinna Vinschen
2014-04-11 23:36 ` Ken Brown
2014-04-12 11:13   ` Corinna Vinschen
2014-04-12 14:20     ` Ken Brown
2014-04-12 14:37       ` Corinna Vinschen
2014-04-15 21:15       ` Ken Brown
2014-04-16  8:04         ` Corinna Vinschen
2014-04-16  9:35           ` Corinna Vinschen
2014-04-16 15:28             ` Ken Brown
2014-04-16 15:32               ` Ken Brown
2014-04-16 15:43                 ` Corinna Vinschen
2014-04-13 10:20 ` Andrey Repin
2014-04-14  8:35   ` Corinna Vinschen
2014-04-14  9:20     ` Andrey Repin
2014-04-14 10:24       ` Corinna Vinschen
2014-04-14 23:05         ` Andrey Repin
2014-04-15  8:37           ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140411122240.GD23281@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).