Created
April 23, 2015 16:44
-
-
Save shaief/292ef36d257d4c64a65c to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' | |
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' | |
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' | |
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' | |
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' | |
Warning (emacs): Python shell prompts cannot be detected. | |
If your emacs session hangs when starting python shells | |
recover with `keyboard-quit' and then try fixing the | |
interactive flag for your interpreter by adjusting the | |
`python-shell-interpreter-interactive-arg' or add regexps | |
matching shell prompts in the directory-local friendly vars: | |
+ `python-shell-prompt-regexp' | |
+ `python-shell-prompt-block-regexp' | |
+ `python-shell-prompt-output-regexp' | |
Or alternatively in: | |
+ `python-shell-prompt-input-regexps' | |
+ `python-shell-prompt-output-regexps' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi shaief, I'm getting the same Warning when I launch the Python REPL. I've noticed that it happens in with WinPython (http://winpython.github.io/), but not with Anaconda. The warning appears but is harmless. Still its annoying, did you find a way around it? Thanks...