public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Mario Emmenlauer <mario@emmenlauer.de>, cygwin@cygwin.com
Subject: Re: Could rm remove files and folders with colon in their name?
Date: Wed, 10 Nov 2021 17:49:20 +0300	[thread overview]
Message-ID: <1563129461.20211110174920@yandex.ru> (raw)
In-Reply-To: <e2bbb443-b876-40fe-ca58-ab0c7d064f7b@emmenlauer.de>

Greetings, Mario Emmenlauer!


> Dear All,

> I've searched if this topic has come up before but could not find it.

> Could 'rm' support removing files and folders that have a colon ':' in
> their name? I.e. I would like that 'rm -fr' would remove a full directory
> tree, including such folders. Currently it will correctly remove anything
> inside such folders, but not the folder itself.

> As an example, for the following structure:
>      C:/root/folder/C:/inside/file.txt

> When using 'rm -fr root', afterwards I have:
>      C:/root/folder/C:

> To remove everything, I can use 'find root -depth -exec rmdir \{\} \;'

> I understand that files and folders with colon in their name are illegal
> on Windows and not supported very well.

They are not necessarily illegal, it's just not well supported.

> But a number of tools manage to create (and also remove) such files. I've
> found that even the native 'del' can support this when using the UNC name
> (see for example https://serverfault.com/a/96833). It would be great if
> Cygwin could also feature this support.

> PS: These folders are created when I use the Cygwin-based build system
> for ICU (see
> https://unicode-org.github.io/icu/userguide/icu4c/build.html#how-to-build-and-install-on-windows-with-cygwin)
> For me this is in a combination with native Perl for Windows (ActivePerl,
> in my case), and using absolute build paths. After using ICU's build
> system, I can not remove the build tree anymore. It may be possible to
> solve this on the ICU side too. But their automake-and-Perl-based path
> mangling is not easily modified, and I've failed to isolate the root
> cause of the illegal paths.

Mixing Cygwin and native tools like that is prone to cause issues. In your
case, it may be more than one issue, as build system could misdetect the
platform it is building on, and such unusable paths could be the least of your
issues.


-- 
With best regards,
Andrey Repin
Wednesday, November 10, 2021 17:45:57

Sorry for my terrible english...


  parent reply	other threads:[~2021-11-10 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  9:45 Mario Emmenlauer
2021-11-10 13:49 ` Corinna Vinschen
2021-11-10 20:24   ` Mario Emmenlauer
2021-11-10 20:39     ` Corinna Vinschen
2021-11-11 14:00       ` Mario Emmenlauer
2021-11-24 15:40       ` Chris Wagner
2021-11-10 14:49 ` Andrey Repin [this message]
2021-11-10 16:35 ` Brian Inglis
2021-11-10 20:23   ` Mario Emmenlauer

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=1563129461.20211110174920@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=mario@emmenlauer.de \
    /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).