gtk4-node-editor(1)

👑 gtk4-node-editor

okay so this is the gtk4-node-editor page from the GTK commands manual, bestie — yes the whole manual section is literally just called GTK commands, and this little icon lives there 💅

---

✨ NAME ✨

gtk4-node-editor — view and edit render node files 🎀

---

✨ SYNOPSIS ✨

gtk4-node-editor [OPTIONS...] [FILE]

---

✨ DESCRIPTION ✨

So gtk4-node-editor is a utility that shows and edits render node files. And where do you even get render node files, you ask? 🌸 They can come from, like, the GTK inspector, or they can just be part of the testsuite in the GTK sources. Iconic sourcing, no notes.

GTK developers use gtk4-node-editor for debugging and testing, and it has built-in support for saving testcases as part of the GTK testsuite ✨ which is genuinely so convenient of it.

---

✨ OPTIONS ✨

• -h, --help — shows you the application help, bestie 🫶
• --version — shows the program version, periodt ⭐
• --reset — does NOT restore autosaved content, and it removes the autosave files. so like, the autosave is gone-gone 💀 do not press this unless you mean it

---

✨ ENVIRONMENT ✨

• GTK_SOURCE_DIR — you can set this to point at where the GTK sources live, so your testcases get saved to the right location 🎯 If it's unset, gtk4-node-editor checks whether the current working directory looks like a GTK checkout, and if that fails too, it saves the testcase in the current working directory. so it always has a lil home for your testcase, ngl 🙈

---

💖 reminder for the girlies: render node files come from the GTK inspector or the GTK sources testsuite, and this tool is a dev/debugging bestie, not a rando app. iykyk.

---

source: GTK 🦋 and that's the whole page, bestie — the gtk4-node-editor(1) manual entry, served fresh, no cap. go edit some render nodes and slay 💅✨