I would probably start by:
- copy-pasting the code to an editor which makes spaces and tabs visible,
- looking quickly for tab/space mixes, and then
- standardising consistently on one or the other.
This may well be a known or fixed issue – Editorial crashes/exits on out-of-range set_selection()
create an empty file
run a python script workflow action like:
editor.set_selection(4,4) # out of range - buffer empty
Thanks – that's helpful.
The problem is having to sandwich the 'Select from List' between two different Python modules when both populating the list from code and then using its output in further code – having to pass the state of various variables between two modules.
I am doing this mainly with a kind of JSON ping-pong in:
which does work, but I wanted to check that I wasn't getting into more complexity than is really needed :-)
I have personally switched off Settings → Check Spellings in Editorial,
but I agree that it would be very helpful for 1.1 to recognise the iOS → Settings → General → Language
distinction between British English and English
(It is well known that the Americans somehow contrived to skip the 19c – the 1840s in particular – and that while this has left them with pleasantly old-school manners, it has also left them with obviously 18c banknotes and spellings ... )
See the section on Editorial workflows for the TaskPaper syntax here: