-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes python compile command #824
Conversation
- now sets the compile command correctly if python buffers are switched - moves point to end of comint buffer, useful if a breakpoint is set
this enables autocompletion This code still has the bug that point stays in the comint buffer
In the second commit I tried to activate Maybe I am misunderstanding what |
Sorry for the mistakes... made it late last night :-( 👍 👍 Thank you ! |
No problem :-) Strange, in my emacs the cursor switches to the comint buffer for both commands. With SPC m c c point is at the beginning of the buffer and with SPC m c C it is at the end. |
I does the expected behavior on my config, I wonder what could alter this . What's your version of Emacs ? |
24.4.1 on Ubuntu 14.04. We might be talking about slightly different things. Testing without a breakpoint, but an error in the file produces the correct behaviour. |
This is indeed what I have too. Is it something annoying we have to fix or -syl20bnr- On Sun, Mar 15, 2015 at 5:40 PM, Christoph Paulik notifications@github.com
|
It is tolerable for me since I will use SPC m c C if I have set a breakpoint. For me there is no point staying in the python src buffer in that case. |
related to issue #805