I only mentioned Feed Hold for information. I just want a Stop ASAP, without losing position, which means following the acceleration rules. It might also necessitate having to complete the current G-code line (which could in some cases be a long move) if the program doesn't want to get too complicated.
But it's not doing that. It's keeping a LONG buffer of operations around that it has to do through- for this 3D carving, there's a lot of moves in the 1 sec it takes to Stop, and yet still seems to fail to use acceleration rules, assuming the error message that comes up is accurate.
Knowing FeedHold takes even longer- 2 sec- is stranger knowing that it's taking longer than the commands already buffered. But FeedHold seems to be the only way to accomplish a "correct" pause, provided the reason for the pause isn't too urgent. Pushing "Stop" seems little different than "E-Stop" right now- you lose position, which seems to make it useless.
BTW, also, hitting FeedHold THEN Stop doesn't cause the "ethernet SmoothStepper ran out of data and probably lost position" error. For what it's worth.