PREFIX(nged)

Changes the name of all the objects listed by adding the specified new_ prefix.

πŸ“… published 7.44.0, from nixpkgs unstable

Okay so boom πŸ’– this is the PREFIX(nged) page β€” the prefix command from the nged manual in the BRL-CAD User Commands lineup, and yes, it gives your objects a whole new-name glow-up. Buckle up, bestie.


✨ NAME ✨

prefix β€” changes the name of all the objects listed by adding the specified new_ prefix. That's it, that's the main character energy.

πŸŽ€ SYNOPSIS πŸŽ€

prefix {new_prefix objects>}

No cap, that's the exact synopsis β€” braces and angle bracket included. We do not "fix" the vibe here. πŸ’…

🌸 DESCRIPTION 🌸

Okay so here's the tea: prefix changes the name of all the objects you list by adding the new_ prefix you specify. Every object gets that prefix tucked onto the front, like a lil name accessory. ✨

And the important part? All references to those objects get changed too. Not just the object names sitting there looking cute β€” the references follow along. So if you rename it, the whole graph knows. πŸ’–

The mvall command performs a similar function. So if you're like "wait, isn't there another one?", yeah, mvall is the cousin with similar-function energy. 🫢

🌈 EXAMPLES 🌈

This example shows the prefix command changing the names of specified objects and all references to them. Literally the whole point, and it ate. πŸ’…

⭐ Example 1. Change the names of specified objects and references to them.

mged>prefix test_ group1 regiona shapeb

That changes the names of objects group1, regiona, and shapeb to test_group1, test_regiona, and test_shapeb. All references to these objects will reflect the new names. No stale old-name vibes left behind, fr fr. πŸ¦‹

Tiny source-detail note: the original prose shows those new names with some funky trailing punctuation, like test_group1,Β”, test_regiona,Β”, and test_shapeb.Β”. The new names themselves are test_group1, test_regiona, and test_shapeb; all references to these objects will reflect the new names. πŸ™ˆ

πŸ‘‘ AUTHOR πŸ‘‘

BRL-CAD Team β€” iconic, honestly.

πŸ’Œ BUG REPORTS πŸ’Œ

Reports of bugs or problems should be submitted via electronic mail to devs@brcad.org. If something's acting cursed, tell the team β€” do not suffer in silence, bestie. 😭


πŸ’– Sign-off cuteness: this page is from the BRL-CAD manual, PREFIX(nged) chapter β€” and the footer didn't give a date, so we're not inventing one, periodt. πŸ’–

πŸ“¦ where this page comes from