Unless the person reading the code has the same tab settings as the person writing the code, the indentation will be messed up by tabs (and indentation is very important for reading LISP languages).

Unfortunately, adding in validation for that edge case gets a bit messy. I’d prefer a more elegant solution, but here it is anyway: Again for readability and to simplify debugging, small functions with clear purpose are easier to read and verify. If we don’t bother with that edge case where the selection starts at the beginning of an existing label, I think this code is reasonably easy to read: ;type toolYou will simply need to supply us a number range and leave a space on your artwork for us to add the number. You can let us know the font, along with font size and we can do the rest. We can insert the various numbers directly into your artwork, there is no need to create hundreds of different artwork files as our designers will do this for you.

We can print any artwork you choose to upload. However, we do reserve the right to reject any that may be indecent, inflammatory or illegal in any way. I’ve not tested on Audacity 2.4.2 as I don’t have that version readily available). ;nyquist plug-in Look to see if some of those global variables can be made local to functions. Global variables aren’t bad per se, but they are a common cause of bugs, and anyone reading the code has to jump around to follow the flow.