I didn't see any different behavior whether the backslash preceded '?' or any normal character (hence the 'x' in my example). Maybe it is different with '*', I didn't check that and it is not my use-case.
-----Original Message----- From: Eli Zaretskii <[email protected]> Sent: Friday, 21 May 2021 5:58 PM To: Ronald Hoogenboom <[email protected]> Cc: [email protected]; [email protected] Subject: Re: basename function in 4.3 cygwin > From: Ronald Hoogenboom <[email protected]> > CC: "[email protected]" <[email protected]>, "[email protected]" > <[email protected]> > Date: Fri, 21 May 2021 15:17:53 +0000 > > As I said, possibly not a bug, but a change in functionality nevertheless. > It is all about what you consider to be "the directory part" and this > consideration has apparently changed. Not in the native port of Make, it didn't (I just tried). Maybe in the Cygwin port, which I don't have. > The root cause of this is (as always) the dual meaning of a backslash: an > escape character or a path separator. Maybe a better way of escaping would be > single-quoting it. Note that in my real use-case, the character after the > backslash is a '?', which needs to be passed un-molested by the shell. I have > some weird experiences with single quoting in makefiles, though. AFAIK, the Windows port treats the backslash as a quote character where it makes sense (e.g., in wildcards).
