MATCH(nged)

list database objects whose names match a wildcard expression

📅 published 7.44.0, from nixpkgs unstable

💅 MATCH(nged) — the wildcard match era

okay bestie, welcome to MATCH(nged), the BRL-CAD user command that's about to make hunting down objects in your database feel like scrolling your fave playlist instead of digging through a filesystem. grab a snack, this one's short and sweet 🍓

✨ NAME ✨

match — lists database objects whose names match a wildcard expression. that's it, that's the whole vibe. no cap 🎀

🌸 SYNOPSIS 🌸

match expression [expression ...]

one expression? cute. five expressions? also valid, main character energy either way ✨

🦋 DESCRIPTION 🦋

the match command lists all the database objects whose names match one or more wildcard expression patterns. literally all of them that fit. 👑

each expression gets matched independently against every object name in the database, using standard path-matching wildcard rules — the exact same rules bu_path_match uses, iykyk. here's the wildcard cheat sheet:

  • * — matches any sequence of characters, including none at all (yes, zero characters counts, she's flexible 💅)
  • ? — matches any single character, one and done
  • [...] — matches any character in the set

then the names of all matching objects get printed. and if you hand her multiple expressions? she gives you the union of all the matches — everyone's invited to the party 🫶

🧚 EXAMPLES 🧚

Example 1. List all objects starting with hull

mged> match hull*

lists all objects whose names begin with hull — for example: hull.r, hull.s, hull_backup.r. slay, instant glow-up of a list 🌟

Example 2. Match by suffix

mged> match *.r

lists all objects whose names end in .r (typically regions). suffix matching ate, no crumbs 💀✨

Example 3. Multiple patterns

mged> match hull* turret*

lists all objects matching either hull* or turret*. two patterns, one command, union energy, periodt 🔥

💜 SEE ALSO 💜

  • ls(nged)
  • search(nged)

go give the neighbors a visit, they're iconic too 🎀

👑 AUTHOR 👑

BRL-CAD Team — the collective main characters behind all of this 🫶

🌈 BUG REPORTS 🌈

found a bug? a problem? something acting sus? reports of bugs or problems should be submitted via electronic mail to devs@brlcad.org — don't be shy, they want to hear it fr fr 📧

ngl, this page is a whole mood: short, sweet, and it does exactly what it says. no notes. 💅

and that's a wrap on MATCH(nged) from BRL-CAD, bestie — this manual page is brought to you by the BRL-CAD crew, dated the day the page was stamped, and honestly? iconic from header to footer. see you in the next one 🦋💖

📦 where this page comes from