sheets/macros.md said scripts reach "the functions below", now on the scripting API page, and gains a short Writing your own section. The Excel changes table lists Sheets-only functions once, linking to Arrays in Excel for which.
- commit
- 3e632a4abbec94550ac19c0ed03232bb7df102c1
- parent
- caf9120b9d6293f7b2f8db48487718711c394033
- author
- Dami <dami.etoile@gmail.com>
| M | docs/ | 2 | +- |
| M | docs/ | 11 | ++++++++--- |
@@ -29,7 +29,7 @@ What changes on the way:
2929 | Excel pivot tables | Come in as the values they showed; 012's go out as their results, not a pivot |3030 | Excel's sheet protection | Comes in unprotected, with a note saying so: Excel's protection locks cells where 012's only warns. Protected ranges aren't written |3131 | Array formulas (Excel 365's dynamic arrays and older `{=...}` ones) | Come in as formulas that spill again, without the values Excel kept in the cells they spill into |32-| Functions only Sheets has (`SORTN`, `FLATTEN`, `SPLIT`, `REGEXMATCH`, `REGEXEXTRACT`) | Go out as values, counted with the others below |32+| Functions only Sheets has, and array literals holding references | Go out as values, counted in the download's note: see [Arrays in Excel](#arrays-in-excel) |3333 | JEV functions, `#AND#`, formulas naming a sheet that doesn't exist | Go out as values (their `#REF!`, for a missing sheet: Excel would refuse the reference). The download's result counts the formulas saved as values, with an example |3434 | A sheet name Excel can't take as is (spaces at its ends, or the same as another's but for them and case) | Written as one it can: without the spaces, with a number when two would clash (`Plan (2)`); formulas and named ranges naming it name that |3535 | Files past the reader's limits (a zip bomb, 1 GB in one part, 2 GB in all, cells past XFD1048576) | Refused, with a message saying which |@@ -127,7 +127,12 @@ own, so they ask once per session.
127127 128128 Scripts can't read or write files, reach the network, start programs, or129129 read the clock or random numbers: all they can reach is the functions130-below. What a macro can do is what you could do with the keyboard in that131-workbook, which is why it asks before running someone else's.130+of the [scripting API](../reference/macro-api.md). What a macro can do is131+what you could do with the keyboard in that workbook, which is why it132+asks before running someone else's.132133 133-Macros are Starlark scripts you can read and write: the [scripting API](../reference/macro-api.md) lists what they can do.134+## Writing your own135+136+**+ Write a macro** in Manage macros opens a new script in your editor.137+The [scripting API](../reference/macro-api.md) lists the functions138+scripts call and the command ids they run.