POLYRUN(1)

💖 POLYRUN(1) 💖

okay bestie so this is a page from the General Commands Manual, section 1 (that's the "run it in your shell" section, iykyk), and it's all about two lil commands that go find your polygen grammars for you 💅

✨ NAME ✨

polyrun, polyfind — find polygen grammars and run polygen 🦋

🌸 SYNOPSIS 🌸

polyrun [options] grammar
polyfind grammar

🎀 DESCRIPTION 🎀

so here's the vibe. polyrun runs polygen, but before it does that it takes the grammar name you gave it and expands it into its full path, so that polygen can actually find it. no more "where is this file" energy, we love that for us 💖

Grammars can be given as partial paths, like debian/flame (yes, that's the example, no I'm not changing it, it's iconic). And here's where they get searched, in this order, lowkey important:

1. the current directory first 🥇
2. then a subdirectory of /usr/share/polygen according to your current locale settings 🌍
3. then recursively under /usr/share/polygen and all its subdirectories 🔍

also you can write grammars with or without the .grm extension — she's flexible like that, no cap ✨

and polyfind? she's the simpler sister. all she does is look for the full pathname of the grammar you gave her and print it on standard output. that's it. that's the whole job. queen behavior 👑

🫶 OPTIONS 🫶

• polyrun is literally just a wrapper to polygen, so every option you hand her gets passed to polygen as-is. no filter, no processing, straight through 🏃♀️
• polyfind takes only the grammar name as argument. no options, no extras, she's a one-argument girlie 🙈

bestie heads up: since polyrun just forwards everything to polygen, go read polygen(1) for the actual option list — this page isn't the one holding those secrets 💀

🌈 SEE ALSO 🌈

• polygen(1)
• polygen-data(6)

💜 AUTHOR 💜

polyrun/polyfind and this very manpage are written and maintained by enrico@enricozini.org 🫶

and that's the whole page, bestie!! this beauty is dated October 2, 2006 and it lives in the General Commands Manual — we stan a vintage legend 👑✨💅