Inquiry about EmmyLua Debugger Behavior After Clicking "Stop" in Cursor Editor

[chengxuyuanYYS]

ello,
I'm using the EmmyLua plugin in the Cursor editor. I've noticed that when I start a debugging session and later click the "Stop EmmyLua" button at the bottom of the editor, the debugger doesn't seem to fully disconnect. I can still use the "Run and Debug" feature to debug my Lua code without restarting the application.
Could you explain the underlying mechanism behind this behavior? Specifically:
Why does the debug session remain active after clicking "Stop"?
Does this indicate that the debug hooks (e.g., debug.sethook) or the socket connection to the Lua process are not fully terminated?
Is this by design, and if so, what is the intended workflow for completely stopping a debug session?
Thank you for your insight

[CppCXY]

Cursor doesn't include an official copy of EmmyLua; you can only install it from the VS Code Extensions Marketplace. Also, the 'Stop' button in the lower-left corner stops the language server, not the debugger, and EmmyLua's debugger indeed doesn't stop hooks so it can reconnect. If you want to completely stop the hooks, the only thing I can suggest is restarting the target program.