On Sun, 28 May 2023, Tim via users wrote:
On Sun, 2023-05-28 at 08:49 -0400, Max Pyziur wrote:
`find . -iname '*pdf' -type f -perm 755`
Searching for "spaces" through the man file for find, I find this:
Safer `find -print0 | xargs -0` approach
• Find files named core in or below the directory /tmp and delete
them, processing filenames in such a way that file or directory
names containing single or double quotes, spaces or newlines are
correctly handled.
$ find /tmp -name core -type f -print0 | xargs -0 /bin/rm -f
The -name test comes before the -type test in order to avoid
having to call stat(2) on every file.
Does that give you some clues?
I just don't use blank spaces in file names and paths. They cause so
many problems that I won't use them. Everything lower-case with either
hyphens or dots as punctuation, nothing else, so I can easily type
things without having to use the shift key. Typing bloody CamelCase
really pisses me off, and I often have to type things in somewhere
where there isn't an actual keyboard.
Thank you.
Yes, likewise I follow the same principles, prefering "Camel-style" names,
e.g. AFilenameSuchAsThis.txt.
The problems arise from files that are produced by others (co-workers,
downloaded, etc).
MP
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
