sort-pw-cfg(1)

💅 sort-pw-cfg(1) — the manual page, but make it make sense 🎀

okay so real talk, this is the man page for sort-pw-cfg, and yes bestie the manual name is literally right there in the title, we're not hiding it. let's get into it ✨

---

✨ NAME ✨

sort-pw-cfg — sort/merge password config file. that's the whole vibe. it sorts. it merges. it's giving organizational queen 👑

---

🦋 SYNOPSIS 🦋

sort-pw-cfg [-flags] [-flag [value]] [--option-name[[=| ]value]] [ <cfg-
file> ...]

so here's the deal about the operands (the files this program operates on, iykyk): you can name them right there on the command line, or you can pipe them in through standard input, one per line 🫶. and when you do the stdin thing, leading and trailing white space gets stripped, and blank lines are straight up ignored, no cap.

⚠️ heads up: standard input may not be a terminal. so don't just run it raw and expect it to read your mind 💀

---

🌸 DESCRIPTION 🌸

bestie. this program will sort (and merge) the per-domain password attributes. that's its whole personality.

if there are duplicate entries? the last entry seen survives. periodt. the result gets sorted by password id hash code and option name. so like, any file containing more recent entries should appear last — that's the rule 🔥.

and ngl, here's the messy part: if you've updated two different password ids in two different password configuration files without having merged them, you may have a merge problem 😭. and there's no magic fix for that — you will need to try to remember what you did. good luck, soldier 🫡

the "header" portion of the config file (the seeds and the <program...> marker) is taken from the first config file listed and ignored in the remaining files. like, first one wins, everyone else's header is just noise 🙈

example usage? scroll down, it's in the example section below ✨

this program will perform its function for every file named on the command line or every file named in a list read from stdin. and lowkey important: the arguments or input names must be pre-existing files — it's not gonna manifest them for you 🧚

oh and the input list may contain comments! which are blank lines, or lines beginning with a # character. very demure, very mindful 💅

---

💖 OPTIONS 💖

• -o file, --output=file — send result to this file. normally, the first named file gets rewritten with the entries ordered by the hash code with duplicates removed. use this option to redirect output to the named file instead 🎀
• -d, --default — select default config file for first input file. so instead of starting with the first operand (or the first file in the standard input file list), it starts processing password id's with the contents of the standard configuration file. the additional files will then override or augment this file. main character energy fr 👑
• -h, --help — Display usage information and exit. the classic. we love a helpful icon 💅
• -M, --more-help — Pass the extended usage information through a pager. for when you want the full lore 📖
• -v [{v|c|n --version [{v|c|n}]}], --version — Output version of program and exit. the default mode is v, a simple version. the c mode will print copyright information, and n will print the full copyright notice. pick your fighter 🥊

---

🔥 EXIT STATUS 🔥

one of the following exit values will be returned, and yes bestie, memorize these, they're your emotional support numbers:

• 0 (EXIT_SUCCESS) — Successful program execution. slay 💖
• 1 (EXIT_INVALID) — the option/argument configuration is invalid 🙈
• 2 (EXIT_NO_MEM) — insufficient memory 😭
• 3 (EXIT_BAD_USER) — no password entry for current user 💀
• 4 (EXIT_HOMELESS) — home directory could not be found 🏚️
• 5 (EXIT_PERM) — config file improperly protected 🔒
• 6 (EXIT_NO_CONFIG) — config file missing 🫥
• 7 (EXIT_BAD_CONFIG) — cannot update config file 😤
• 8 (EXIT_NO_SEED) — no seeds were specified in the config file 🌱
• 9 (EXIT_BAD_SEED) — The seed value was invalid 🍓
• 10 (EXIT_BAD_SELECT_CHARS) — the list of characters for the --select-chars option is bad 🎭
• 11 (EXIT_NO_PWID) — no password id was specified 🚫
• 16 (EXIT_CODING_ERROR) — There is a coding error that should be reported 🐛
• 70 (EX_SOFTWARE) — libopts had an internal operational error. Please report it to autogen-users@lists.sourceforge.net. Thank you. 🫶

---

👑 AUTHORS 👑

Written by Bruce Korb. we stan a legend 🌈⭐

---

🧚 NOTES 🧚

This manual page was AutoGen-erated from the sort-pw-cfg option definitions. so like, it wasn't even hand-written, the machine did that. iconic behavior honestly 🤖✨

---

and that's the whole page bestie!! 💜 this was version 2.7.4, dated 2020-09-30 — so yes, it's got a little vintage energy, but it still ate and left no crumbs 🍓🦋 go forth and sort those password configs, you've got this 💅🎀