Skip to content
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

Python compile mode #805

Closed
cpaulik opened this issue Mar 11, 2015 · 10 comments
Closed

Python compile mode #805

cpaulik opened this issue Mar 11, 2015 · 10 comments

Comments

@cpaulik
Copy link
Contributor

cpaulik commented Mar 11, 2015

Sometimes using the REPL is very inconvinient. Especially if one changes something in another module we currently have to close the REPL manually and start it again. I much prefer using comint mode for these slightly more complex cases. But doing:

  • SPC u SPC c C
  • change the compile command RET
    can get annoying.

This is why I wrote the code in the PR referencing this Issue. There might be a better way to do this but I'm a elisp newby so excuse any errors.

@sebhahn
Copy link
Contributor

sebhahn commented Mar 16, 2015

there is a problem using the python compile mode feature - open windows are automatically closed and compile result is not shown (tested with spacemacs v0.100.0)

@syl20bnr
Copy link
Owner

Oh this is a "feature" of spacemacs which closes the compilation window if there is no error.
If it is annoying then it can be removed.

@syl20bnr
Copy link
Owner

I close the issue since it is fixed in master now but we can continue to discuss here about the other issue.

@cpaulik
Copy link
Contributor Author

cpaulik commented Mar 17, 2015

Hmm, I don't know if this is easily possible, but I would say that this behaviour is fine for SPC m c c but I would expect the window to stay open if the user wants to switch to the compilation window.

Another idea would to be to maybe add a dotspacemacs-compilation-window-close-delay variable which specifies how long the window should stay open. Do you think this could be useful or annoying?

@sebhahn
Copy link
Contributor

sebhahn commented Mar 17, 2015

I'm fine if it's a feature that the compile window is not shown, but by automatically closing I meant if I have two (or even more) windows open and I'm running SPC m c c one of the windows is closing unexpectedly

@cpaulik
Copy link
Contributor Author

cpaulik commented Mar 17, 2015

Yes closing is maybe not the best solution. If you start with a let's say 3 pane layout and compile twice only one window is left. Maybe it would be better in general to just split the window that is being compiled.

@syl20bnr
Copy link
Owner

I see, the compilation buffer used to be a sticky popup window but it has been removed so the auto-closing can be removed as well.

@remyzorg
Copy link

Hi,

Is there a way, as a spacemacs user, to keep the compilation window opened after compiling is successfull ? Even if I split my screen, the window is closed and it's verry annoying.

For example, compilation command usually includes my tests and outputs and I would like to see them.

@cpaulik
Copy link
Contributor Author

cpaulik commented Apr 28, 2015

@remyzorg (setq compilation-finish-function nil) should work.
@syl20bnr should this be the default or do you have something else in mind?

@remyzorg
Copy link

@cpaulik It works, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants