From: Eric L. <Eri...@ma...> - 2011-03-14 13:19:21
|
RET is bound by comint mode, and matlab-shell just does whatever comint does. comint is a library used for defining modes that interact with a shell like command. I suppose something similar could be replicated in just a shell buffer if that is the case. If it is stuck in matlab.el code, the trick will be identifying which loop it is stuck in. Enabling debugging (M-x toggle-debug-on-quit) would help if it were possible to quit, which leads me to believe it is in a filter or one of the hooks that prevents C-g from working. Eric -----Original Message----- From: Leo Alekseyev [mailto:dn...@gm...] Sent: Sunday, March 13, 2011 4:41 AM To: mat...@li... Subject: [Matlab-emacs-discuss] Possible bug: emacs unresponsive if hit RET multiple times at the end of matlab command Tested with Matlab mode 3.3.1, several recent versions of Emacs. Steps to reproduce: M-x matlab shell pause(10) RET RET RET Here, pause(10) can be any command that doesn't return immediate result. Expected result: Matlab command runs in matlab-shell buffer, Emacs can be used as normal. Observed result: Emacs quits responding to keyboard input until the command exits. This Is a serious problem, as it presents an easy way to accidentally hose your Emacs session when working with long-running commands. Can anybody reproduce and/or comment? --Leo ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Matlab-emacs-discuss mailing list Mat...@li... https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss |