Command line and power tools
Modern filenames contain spaces, accents, symbols and emoji. Each breaks a different tool in a different way.
Finder search and type-ahead deal with any character natively — spaces, accents, emoji, all of it. If a file with an odd name is hard to find, Finder is rarely the problem.
Spaces and symbols break unquoted commands:
cat My File.txt # fails — two arguments
cat "My File.txt" # works
cat My\ File.txt # also works
Glob around unknown symbols instead of typing them:
ls *résumé*
ls *"invoice"*
macOS stores filenames in a specific unicode form (NFD — decomposed), so é is stored as e + a combining accent. A search for the precomposed é (NFC) can miss it. This bites scripts comparing filenames from different sources. Tools like find mostly handle it; exact string matching across systems may not.
find . -iname "*resume*" # -iname is more forgiving than exact matching
They work as ordinary characters. To type one into a search or command, use the emoji picker (⌃⌘Space) rather than pasting from elsewhere, which sometimes carries invisible variation selectors that break exact matches.
/ — impossible in a filename (it is the path separator); Finder shows a typed / as :: — legal but displays oddly, a holdover from classic Mac paths. — hides the fileFor scripting over awkward names, null-delimiting avoids every quoting problem:
find . -name "*émoji*" -print0 | xargs -0 ...
-print0 and -0 pass filenames with embedded spaces, newlines and unicode intact.
The space splits the filename into separate arguments. Quote it ("My File") or escape the space (My\ File).
Yes — they are ordinary characters. Finder handles them; in Terminal, use the emoji picker to type them cleanly.
Everywhere keeps track of every file on your Mac — including the folders Spotlight hides and drives you have unplugged. Free for a day, then $19 once.
Download for Mac