DIRNAME(1P)

💅 DIRNAME(1P) — POSIX Programmer's Manual, bestie edition 🎀

okay so first things first, this page is part of the POSIX Programmer's Manual — it's the manual for dirname, and it lives in the 1P section of the manual, so that's the whole vibe we're working with today. slay

🫶 heads up queen: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so pls consult the corresponding Linux manual page for details of Linux behavior), or the interface may literally not be implemented on Linux at all. 💀

---

✨ NAME ✨

dirname — return the directory portion of a pathname. that's it. that's the whole job. iconic behavior honestly 👑

---

🌸 SYNOPSIS 🌸

dirname string

---

🦋 DESCRIPTION 🦋

okay so the string operand shall be treated as a pathname, as defined in the Base Definitions volume of POSIX.1‐2017, Section 3.271, Pathname. and the string shall be converted to the name of the directory containing the filename corresponding to the last pathname component in string, performing actions equivalent to the following steps, in order, no skipping (except when it says to skip, obviously):

1. If string is //, skip steps 2 to 5. (yes bestie, // is special, we'll get to why later 👀)
2. If string consists entirely of <slash> characters, string shall be set to a single <slash> character. In this case, skip steps 3 to 8.
3. If there are any trailing <slash> characters in string, they shall be removed. ✂️
4. If there are no <slash> characters remaining in string, string shall be set to a single <period> character. In this case, skip steps 5 to 8.
5. If there are any trailing non-<slash> characters in string, they shall be removed.
6. If the remaining string is //, it is implementation-defined whether steps 7 and 8 are skipped or processed. (this is the spicy one, keep reading 😭)
7. If there are any trailing <slash> characters in string, they shall be removed.
8. If the remaining string is empty, string shall be set to a single <slash> character.

and then, the resulting string shall be written to standard output. periodt. 💖

---

🔥 OPTIONS 🔥

None. not a single one. this utility is unbothered, moisturized, in its own lane, thriving. 💅

---

🎀 OPERANDS 🎀

the following operand shall be supported:

• string — a string. just... a string. that's the whole operand. simple queen energy.

---

💜 STDIN 💜

Not used. it does not want your stdin. it has its own string to deal with.

---

🌈 INPUT FILES 🌈

None. nope. no files read here.

---

🧚 ENVIRONMENT VARIABLES 🧚

the following environment variables shall affect the execution of dirname (iykyk, these are the standard POSIX locale girlies):

• LANG — provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
• LC_ALL — if set to a non-empty string value, override the values of all the other internationalization variables. yes, all of them. she's that powerful. 👑
• LC_CTYPE — determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
• LC_MESSAGES — determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
• NLSPATH — determine the location of message catalogs for the processing of LC_MESSAGES.

---

⭐ ASYNCHRONOUS EVENTS ⭐

Default. nothing funky happening here bestie.

---

🍓 STDOUT 🍓

the dirname utility shall write a line to the standard output in the following format:

"%s\n", <resulting string>

so basically the resulting string plus a newline. clean. ✨

---

💀 STDERR 💀

the standard error shall be used only for diagnostic messages. that's it. no random gossip on stderr.

---

🫶 OUTPUT FILES 🫶

None. we're not writing files here, we're just talking to stdout.

---

💖 EXTENDED DESCRIPTION 💖

None. there is no extended description. the description was enough. she said what she said. 💅

---

👑 EXIT STATUS 👑

the following exit values shall be returned:

• 0 — Successful completion. 🎉
• >0 — An error occurred. 😭

---

🙈 CONSEQUENCES OF ERRORS 🙈

Default.

the following sections are informative. (which means they're the fun bonus lore, not the rules-rules 📖)

---

🌸 APPLICATION USAGE 🌸

okay so the definition of pathname specifies implementation-defined behavior for pathnames starting with two <slash> characters. therefore, applications shall not arbitrarily add <slash> characters to the beginning of a pathname unless they can ensure that there are more or less than two, or are prepared to deal with the implementation-defined consequences. like. don't do it unless you know what you're doing bestie, fr fr.

---

🌈 EXAMPLES 🌈

the EXAMPLES section of the basename() function (see the System Interfaces volume of POSIX.1‐2017, basename()) includes a table showing examples of the results of processing several sample pathnames by the basename() and dirname() functions and by the basename and dirname utilities.

See also the examples for the basename utility.

---

🧠 RATIONALE 🧠

the behaviors of basename and dirname in this volume of POSIX.1‐2017 have been coordinated so that when string is a valid pathname:

$(basename -- "string")

would be a valid filename for the file in the directory:

$(dirname -- "string")

and THAT, bestie, is the whole point. 🎯 this would not work for the versions of these utilities in early proposals, due to the way processing of trailing <slash> characters was specified. consideration was given to leaving processing unspecified if there were trailing <slash> characters, but this cannot be done; the Base Definitions volume of POSIX.1‐2017, Section 3.271, Pathname allows trailing <slash> characters. so the basename and dirname utilities have to specify consistent handling for all valid pathnames. no cap. 🔥

---

🦋 FUTURE DIRECTIONS 🦋

None. the future is now and it's still dirname. ✨

---

💜 SEE ALSO 💜

• Section 2.5, Parameters and Variables, basename
• The Base Definitions volume of POSIX.1‐2017, Section 3.271, Pathname, Chapter 8, Environment Variables
• The System Interfaces volume of POSIX.1‐2017, basename(), dirname()

---

📜 COPYRIGHT 📜

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

and that's the whole page, bestie!! 🎀 this edition of dirname(1P) is brought to you by IEEE/The Open Group, dated 2017, from the POSIX Programmer's Manual — go forth and strip those trailing slashes like the main character you are. 💅✨🦋