PATHCHK(1)

πŸ’– pathchk(1) β€” the "is this filename even valid tho" check πŸ¦‹

okay bestie, so this is pathchk, a lil tool from the General Commands Manual section of your friendly neighborhood manual pages, and it's about to be your new hyperfixation, fr fr. πŸ’…


✨ NAME ✨

pathchk β€” Check whether file names are valid or portable πŸ‘‘


🌸 SYNOPSIS 🌸

pathchk [OPTION]... NAME...

πŸŽ€ DESCRIPTION πŸŽ€

Check whether file names are valid or portable πŸ’–

that's it. that's the whole job. you hand it some names, it vibe-checks them and tells you if they'd survive out there on other systems. no cap. ✨


🌈 OPTIONS 🌈

  • -p β€” check for most POSIX systems 🫢
  • -P β€” check for empty names and leading "-" 😭 (yes, the sneaky ones that start with a dash, we see them)
  • --portability β€” check for all POSIX systems (equivalent to -p -P) πŸ”₯ both modes, all at once, main character energy
  • -h, --help β€” Print help πŸ™ˆ
  • -V, --version β€” Print version ⭐

πŸ‘‘ VERSION πŸ‘‘

v(uutils coreutils) 0.12.0 β€” yes she has a version and yes she serves


πŸ¦‹ EXAMPLES πŸ¦‹

Check pathnames for validity in the current system:

pathchk path1 path2 ...

Check pathnames for validity on a wider range of POSIX compliant systems:

pathchk -p path1 path2 ...

Check pathnames for validity on all POSIX compliant systems:

pathchk [-p -P|--portability] path1 path2 ...

Only check for empty pathnames or leading dashes (-):

pathchk -P path1 path2 ...

The examples are provided by the tldr-pages project <https://tldr.sh> under the CC BY 4.0 License. Please note that, as uutils is a work in progress, some examples might fail. πŸ’€ (it's giving "work in progress" and we respect the honesty)

πŸ’œ a lil sign-off πŸ’œ

this page is dated 2026-09-25 and lives under the name pathchk(1), so if you're citing her in your little blog post, that's the receipt bestie 🧚 stay valid, stay portable, and remember: check your pathnames before you ship them βœ¨πŸ“πŸ’–

πŸ“¦ where this page comes from