It would be helpful to be able to pause a gesture in order to perform another action and then have the gesture continue off from where it left off.
My thought would be do either include an llDialogue type step with two buttons that would allow the gesture to continue or allow something like Wait: -1.0 seconds to indicate a forced pause where the gesture command would then need to be typed again in the chat window in order for the gesture to complete.
My initial thought would lean towards the 2nd method as you could then use this to establish a timeout limit after which time the gesture would be officially be considered to be completed.
So for example:
Gesture (Trigger /start)
Animation: Teaching_Pose
Chat: Welcome to xxxx
--- Wait: 2.0 seconds
Chat: Please take a copy of the class materials in the center of the room
--- Wait: -1200.0 seconds
...
You would then type in /start to start off the gesture. The gesture would hit the negative time for the wait command which then signals to SL that the user has up to x amount of time (10 minutes in this case) to do other things while it waits for the /start trigger to be re-entered on the command line. At which point the gesture continues at line 6 rather than starting back at line 1 again.
The alternative method:
Gesture (Trigger /start)
Animation: Teaching_Pose
Chat: Welcome to xxxx
--- Wait: 2.0 seconds
Chat: Please take a copy of the class materials in the center of the room
Dialogue: /startprev, /start, /startnext
...
Would display a standard llDialogue box in the upper right hand corner where the user could then define up to three buttons. When the gesture hits the dialogue library step the gesture would pause --- allowing you to do some something else, and then resume using one of the 4 options available on the dialogue box (button 1, button 2, button 3, or ignore). The ignore would terminate the gesture. If the trigger (/start) was used as one of the button options then the gesture would pick up at the next line in the gesture. If one of the other buttons is selected then the gesture would terminate and say whatever that text was in the main chat window. Again this relies on the pause needing the trigger to be re-entered in order to resume the gesture.
Of course if we aren't worried about timing out or forcing the gesture to end early the Library command could just be a simple Pause step and its up to the user to manually reenter the trigger again without worring that the gesture might never complete (See next example)
Gesture (Trigger /start)
Animation: Teaching_Pose
Chat: Welcome to xxxx
--- Wait: 2.0 seconds
Chat: Please take a copy of the class materials in the center of the room
--- Pause
...
I wouldn't suggest this however only because I would think if someone started piling up a whole pile of gestures this way they could eventually crash either their session or potentially the sim depending on how the gesture effects server side resources.
Just thinking out loud at this point.