query: Any reason why find does not merge multiple slashes into one?
positive_passages.docid: 144974
positive_passages.text: Why does find print a leading './' if no paths are given?
negative_passages.docid: 39507
negative_passages.text: How can I store the "find" command results as an array in Bash
negative_passages.docid: 122511
negative_passages.text: Command "find -name" must be enclosed in quotes or it doesn't work. Why is that?
negative_passages.docid: 69143
negative_passages.text: Why can't I end a raw string with a backslash?
negative_passages.docid: 154437
negative_passages.text: Regex: match first slash in url -- thats it!! ? not working for some reason?
negative_passages.docid: 56125
negative_passages.text: \( \) don't work with TOC?
negative_passages.docid: 32628
negative_passages.text: How to combine 2 -name conditions in find?
negative_passages.docid: 127525
negative_passages.text: Regular Expression for getting everything after last slash
negative_passages.docid: 107289
negative_passages.text: Why can "find" not be used in PowerShell?
negative_passages.docid: 102108
negative_passages.text: How do I use find when the filename contains spaces?
negative_passages.docid: 143918
negative_passages.text: Why won't this Path.Combine work?
negative_passages.docid: 73784
negative_passages.text: Avoid a trailing slash in bash when completing a directory name (like zsh)
negative_passages.docid: 122830
negative_passages.text: findstr DOS Command's multiple string argument
negative_passages.docid: 158157
negative_passages.text: What does “{} \;” mean in find (in Linux)?
negative_passages.docid: 118739
negative_passages.text: Can I create an element with forward slash as part of the name
negative_passages.docid: 12822
negative_passages.text: GNU find and masking the {} for some shells - which?
negative_passages.docid: 151693
negative_passages.text: What does "{} \;" mean in the find command?