Re: Solved. Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ...

Nothing new here; only correction of mistakes that I made (I decided to review my e-mail because Ken Brwon took an interrest in the subject matter). On Fri, 06 Sep 2019 23:53:05, Houder wrote: > To those still interested! :-P [snip] > While I took a closer look at the source code, I found a BUG

Re: Solved. Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ...

On Sat, 21 Sep 2019 21:02:37, Ken Brown wrote: [snip] > I think you can simplify this by eliminating the second part and changing > the first part to the following: > > char sep = dir[strlen (dir) - 1]; > if (isdirsep (sep) >{ > /* This converts // to

Re: Solved. Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ...

On 9/6/2019 5:53 PM, Houder wrote: > However an exception can be made for e:/ (or e:\), as follows: > > -- >char flag = '\0'; >// strip trailing dirsep's, while remembering the last one >if (isdirsep (dir[strlen (dir) - 1])) > { >flag = dir[strlen

Solved. Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ...

To those still interested! :-P I expressed surprise that mkdir e:/ does NOT refer to the drive, but rmdir e:/ does. Likewise do ls, stat ... https://cygwin.com/ml/cygwin/2019-08/msg00334.html ( Odd, is it not? mkdir 'e:\' cannot be undone by rmdir 'e:\' ... ) Why could mkdir not be made