DZEDIT(1)

💅 dzedit(1) — the CERN ZEBRA documentation editor 🦋

okay so bestie, gather round, because this one's a little vintage gem from the CERN vaults and the man page is, and I say this with love, completely unhinged. let's get into it ✨

---

🌸 NAME 🌸

dzedit — the CERN ZEBRA documentation editor. that's the whole name. that's the whole vibe. periodt.

---

🎀 SYNOPSIS 🎀

dzedit  [ options ]
dzeX11

yes bestie, there are two of them. one is the wrapper, one is the actual program. we'll get there 💜

---

✨ DESCRIPTION ✨

so dzeX11 is an interactive interface to the DZDOC system — which is the ZEBRA documentation system, developed at CERN, no big deal 💅. and dzedit? dzedit is a wrapper script around dzeX11 that lets you set a few environment options. it's giving personal assistant energy, honestly 🫶

now, context, because iykyk: ZEBRA is part of the Packlib library, and it's the thing that lets a developer create complex data structures in the FORTRAN 77 language. and then the DZDOC system is the whole reason we're here — it lets the developer generate and maintain documentation of ZEBRA data structures. iconic behavior, no cap 📚

---

💖 OPTIONS 💖

• -d driver — use the graphics driver driver, i.e., make dzedit call the program dzedriver. the default is "X11". and ngl? you are exceedingly unlikely to want anything other than the default. like, genuinely. don't be quirky about this one 🙈
• -h host — give the host to open the window on. this is functionally the same as setting the environment variable $DISPLAY to "host:0.0". and bestie, you do not need to do this if you're logged on to a remote host through SSH (and if you're using telnet? shame on you! 😭 fr fr, we talked about this).
• -v version — specify the version of CERNLIB to use. ok but real talk, this only makes sense if you have a version of CERNLIB directly from CERN installed 👑. in that case you should also have set the environment variable $CERN. then dzedit will look for the dzeX11 program in the directory $CERN/<version>/bin/. slay, path resolution, slay 🗂️

---

🦋 FILES 🦋

• dzedit.kumac — dzedit tries to read startup commands from this file in the <italique>current directory</italique>. it's the little pre-game ritual 🌸
• dzedit.las — dzedit stores the names of the ZEBRA file and documentation file in this file in the current directory. memory keeping 💾
• last.kumac — at the end of a session, dzedit outputs this file containing a transcript of the commands used during the session. it's literally the group chat receipts of your whole sesh 😭📝

---

🌈 SEE ALSO 🌈

the ZEBRA manual, bestie:

http://wwwasdoc.web.cern.ch/wwwasdoc/psdir/zebra.ps.gz

and specifically? chapter 16 is the one about DZDOC. that's your chapter. go read it (or don't, see below 💀).

---

💀 BUGS 💀

okay so this is my favorite part of the entire page and i need you to sit down for it 🫶

this man page is described — by its own self — as essentially useless, because the section of the ZEBRA manual about DZDOC is incomprehensible and there are no tutorials about it. 😭😭😭 the self-awareness is off the charts. main character energy honestly 👑

and the author says: anyone who wants to provide a better man page is welcome to do so. so like… if you're feeling brave? the door is open. your moment. 🚪✨

---

👑 AUTHOR 👑

this manual page was written by Kevin McCarty <kmccarty@debian.org> for the Debian GNU/Linux system (but may be used by others). king behavior, writing the man page and then immediately dunking on it 💜

---

okay that's the whole page bestie, you're officially DZDOC-pilled 🧚

signing off from the General Commands Manual, dated April 15, 2004 — yeah she's vintage, she's a classic, she's DZEDIT(1) and she ate 💅🎀