llines(1)

💖 llines — like, the LifeLines genealogy program, bestie 💖

Ok so first things first: this is a page from the General Commands Manual, and the star of the show is llines(1). Buckle up 🎀

---

✨ NAME ✨

llines — the LifeLines genealogy program. That's it, that's the vibe. 👑

---

🌸 SYNOPSIS 🌸

llines [OPTION]...
llines [OPTION]...Database

Two ways to run her: options only, or options plus a database name right at the end. No space between them, iykyk. 🦋

---

💅 DESCRIPTION 💅

llines invokes the LifeLines genealogy program. Literally just... launches it. That's the whole job.

For up to date documentation please refer to the Documentation section of this man page. (Yes, it says that in the man page. Recursive queen behavior. 🫶)

LifeLines is a program to manipulate genealogical information in lineage-linked GEDCOM format. It has a curses interface, and a built-in interpreter for its own genealogical report language. So you get a full-screen terminal UI and a whole little scripting language living inside it. It's giving main character energy, no cap. ✨

---

🔥 OPTIONS 🔥

The following options are some of the options available for llines. (Read that again: some of. There are more lurking, these are just the ones on the invite list. 🙈)

• -C — Specify configuration file location. Point her at where the config actually lives.
• -F — Finnish option (only available if compiled with Finnish flag). No flag, no Finland. 🧊
• -I — Specify a user property (e.g. -ILLEDITOR=gvim). Set a property right from the command line, iconically.
• -a — Log dynamic memory operation (for debugging). Memory nerd hours. 🔍
• -c — Supply cache values (eg, -ci400,4000f400,4000 sets direct indi & fam caches to 400, and indirect indi & fam caches to 4000). Numbers go brrr. 🍓
• -d — Developmental/debug mode (signals are not caught). Heads up: in this mode signals are not caught. 💀
• -f — Force open a database (only for use if reader/writer count is wrong). Only reach for this if the count is wrong — fr fr, that's the rule.
• -i — Open database with immutable access (no protection against other access -- for use on read-only media). Immutable access, zero protection from other access. Read-only media only, bestie.
• -k — Always show key values (normally key is not shown if a REFN is shown). Normally she hides the key when a REFN shows up; this says nah, show both.
• -l — Lock (-ly) or unlock (-ln) a database for use with read only media (access to a locked database is treated as immutable). Locked = access gets treated as immutable. 🔒
• -n — Do not use traditional family rules. Traditional rules? Declined. 🙅‍♀️
• -o — Specify program output filename (eg, -o/tmp/mytests). Note it's smushed right up against the path, no space.
• -r — Open database with read-only access (protect against other writer access). Protects you from other writers. ✋
• -uCOLS,ROWS — Specify window size (eg, -u120,34 specifies 120 columns by 34 rows). Resize the whole vibe. 📐
• -w — Open database with writeable access (protecte against other reader or writer access). Writeable access, and yes it protects against other readers and other writers. (Spelling of "protecte" is the manpage's, we don't touch it. 💀)
• -x — Execute a single lifelines report program directly. One report, straight to the face. ⚡
• -z — Use normal ASCII characters for drawing lines in user interface rather than the vt100 special characters. ASCII lines only, no fancy vt100 box-drawing. 🌈
• -? — Display options summary, (on UNIX or Linux use the -h option). On UNIX or Linux, go with -h instead. 🫶

---

Also, adjacent besties you should know about:

• llexec is a version of llines without the user interface for non-interactive processing of report programs. (Typically used with the -x option.) So: all the report-running, none of the curses UI. 🤖
• dbverify is a utility program to verify Lifelines databases. For information about options, run dbverify with the -h option. 🩺

---

🧚 FILES 🧚

Possible locations for Lifelines configuration file — Lifelines looks for a configuration file for various settings. See section System And User Properties in the userguide for details.

• /etc/lifelines.conf
• ~/.linesrc
• ~/lines.cfg
• ./linesrc
• ./lines.cfg

Five spots, she'll go looking in all of them. 🎀

---

👑 DOCUMENTATION 👑

The LifeLines documentation should be installed as part of the installation, and may also be viewed at the project site: https://lifelines.github.io/lifelines/

Look for ll-userguide and ll-reportmanual (with appropriate extensions for text, html and pdf formats). The normal installation process includes a large number of sample report programs that you can customize to suit your needs. In the directory containing these reports you should find a file named index.html which gives a very brief summary of each report. 🌟

So like... go read the docs, they're literally right there, and index.html is the tl;dr cheat sheet. iykyk. 💖

---

⭐ SEE ALSO ⭐

llexec(1), dbverify(1), btedit(1) — the whole friend group. 🫶

---

Ngl bestie, if you're poking at a database with -f, -i or -l, re-read those lines first. They're not casual options and the man page says so plainly. 🙈

---

And that's the page! ✨ This was Lifelines 3.2.0, dated 2019 Sep, brought to you by the llines(1) girlies. Periodt. 💅🎀🦋