Open jthaman opened 5 years ago
Not just in emacs, but system-wide
Are you sure this is an ESS problem? Can you check if it happens in other comint-derived modes? For example, if you have python installed, you could do M-x run-python
, and do:
while (1 < 2):
print("Running")
then see if C-c C-c
triggers the same issue.
Thanks. I did some more digging and actually discovered that the problem may have little to do with ESS or comint. It seems this may be a problem with autohotkey. The issue does not occur when I quit a process while autohotkey is disabled.
Hi, in case any other Evil+AHK+Emacs users find this issue frustrating, map comint-interrupt-subjob
to another key on the inferior ESS mode map. I have
(general-define-key
:states 'normal
:keymaps 'inferior-ess-mode-map
":" 'comint-interrupt-subjob)
In my config, which fixes the problem for me. Replace ":" with any single key you don't use in iESS.
Actually, this may be unrelated to AutoHotkey. I have a new windows computer and am encountering the same issue without using AHK.
It's not ESS related. Might not even be Emacs related. To me it looks like your Alt key is locked by display or window manager somehow.
Do you know what it means if my ESS buffer looks like:
(R): ess-dialect=R, buf=JAGM/test.R, start-arg=nil
current-prefix-arg=nil
(inferior-ess: waiting for process to start (before hook)
(inferior-ess 3): waiting for process after hook(R): inferior-ess-language-start=options(STERM='iESS', str.dendrogram.last="'", editor='emacsclient', show.error.locations=TRUE)
eisabling output delimiter because CMD failed to parseDisabling output delimiter because CMD failed to parseDisabling output delimiter because CMD failed to parseDisabling output delimiter because CMD failed to parseDisabling output delimiter because CMD failed to parseDisabling output delimiter because CMD failed to parse
The output at the end is strange, and might show up when I encounter this issue.
Do you configure R prompt by any chance? Those errors are from the internal communication with the process. Hard to tell what's going wrong.
Any tips that I could apply to try to debug the messages?
I don't customize the prompt. I do apply to special fontifications, but that's just theming. I don't touch inferior-ess-primary-prompt
or the like.
Customization of prompt is on the R side with options()
.
You can insert (message "%s" cmd)
inside ess-command
just before the above message and see which cmd is triggering it.
Hi, I have an issue with ESS 18.10 on Windows 10 with Emacs 26.1. It seems that after I quit a running R computation with
C-c C-c
in an iESS buffer, all subsequent keystrokes are interpreted as if the Alt key is held down. It's very strange. Here is a minimal init.el I was using.Open a buffer in R-mode and fill it with these contents.
I run the code chunk with
C-c C-c
and this opens up an R process in an iESS buffer. Switch over to the iESS buffer and kill the running code withC-c C-c
. Now Windows 10 starts to act like the Alt key is held down. Not just in emacs, but system-wide. Pressing the Alt key again returns the Alt key to normal.This only happens on my Windows 10 computer, and it happens every time I
C-c C-c
in an iESS buffer. No problem like this on Ubuntu.