I've noticed a strange connection between changing accelerator bindings for key combination and command line stacking. The problem manifests itself when you have a string not containing a stacking charater assigned to an accelerator and then change it to one containing such a character. This only seems to happen when you load accelerators from a script file, and works correctly when you try it from the command window.
For example, loading a file with the following snippet:
Hitting Ctrl+8 (with a * alias sending to output defined) produces the expected "northneast" in the output window. Then reloading the script with the second line uncommented:
Will continue to give "northneast" until you go into the respective configuration dialog and change the status of the command stacking option (regardless of whether it was disabled or enabled). Then (without reloading the script) Ctrl+8 produces what it should: either "north" followed by "east" on the next line if you've enabled stacking, or "north;east" if you disabled it.
In other words, this is pretty obscure.
For example, loading a file with the following snippet:
Accelerator ("Ctrl+8", "northneast")
--Accelerator ("Ctrl+8", "north;east")
Hitting Ctrl+8 (with a * alias sending to output defined) produces the expected "northneast" in the output window. Then reloading the script with the second line uncommented:
Accelerator ("Ctrl+8", "northneast")
Accelerator ("Ctrl+8", "north;east")
Will continue to give "northneast" until you go into the respective configuration dialog and change the status of the command stacking option (regardless of whether it was disabled or enabled). Then (without reloading the script) Ctrl+8 produces what it should: either "north" followed by "east" on the next line if you've enabled stacking, or "north;east" if you disabled it.
In other words, this is pretty obscure.