Where next
You now know enough MaSH to read and write real automations. Here’s where to go next.
For the exact rules
Section titled “For the exact rules”The language reference states precisely how the language behaves: every keyword, the order operators apply in, how values convert, how scope works. Use it when you want an answer rather than a lesson.
For every object and method
Section titled “For every object and method”The library reference documents everything under mash: files, fields, users, groups, CSV, PDF, images, mail, SMS, HTTP and the rest, with each method’s arguments and what it returns.
For recipes
Section titled “For recipes”The how-to guides take a real job and show a complete script for it, such as filing documents by order number, logging a document’s fields to a CSV, and redacting sensitive text from PDFs.
Habits worth keeping
Section titled “Habits worth keeping”- Start small and run often. Run after every few lines. The Output panel is your friend.
- Print what you’re unsure of.
printlinea value to see what it really holds. - Guard first. Check the file, the fields and the settings before doing any work.
- Prefer copy to move, and test on a test share.
- Add an
errorblock. A script that fails quietly is worse than one that says so. - Read the log. Settings > MaSH > Logs shows every run, with its output and any unhandled errors.
Ask Grace in the editor to explain or draft a script. She writes MaSH, and she can read yours. Check what she writes before you rely on it, as you would a colleague’s work.