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

compilation keybindings proposal #5987

Closed
phinicota opened this issue May 5, 2016 · 1 comment
Closed

compilation keybindings proposal #5987

phinicota opened this issue May 5, 2016 · 1 comment
Labels
- Mailling list - Key Bindings stale marked as a stale issue/pr (usually by a bot)

Comments

@phinicota
Copy link

phinicota commented May 5, 2016

I would like to propose the following keybindings to the SPC c (Compilation) function:

Keybinding Function
SPC c r repeat last compilation
SPC c Q close all compilation windows opened
SPC c d close last compilation window
SPC c q close compilation window in current frame
SPC c s show last compilation buffer in current frame
SPC c S show and focus last compilation buffer

I wouldn't call these "issues", but this is why I think my proposal is an improvement:

  • SPC c r: currently only repeats last compilations issued with SPC c C (and SPC c c probably?) but it won't recompile SPC p c (projectile-compile-project) for instance.
  • SPC c d and SPC c q: was recently remapped to SPC c d to be consistent with SPC w d, but this last one closes currently focused window, not last. So maybe we could keep one keybiding for last compilation buffer (SPC c d) and one for inside current frame compilation buffer (SPC c q)?
  • SPC c Q: and then the one to rule them all to get rid of all opened compilation buffers.
  • SPC c s and SPC c S: due to the recent change to SPC e n being remapped to compilation-next-error instead of flycheck-next-error only when a compilation buffer is opened, once you hide the compilation buffer or close it, you lose the ability to navigate between errors, so opening it up again could be useful to continue navigation (instead of having to re-launch compilation?).

Might be worth noting I'm thinking these for a emacs-daemon & emacsclient kind of workflow. Don't know if/how it would work elsewhere.

@phinicota phinicota changed the title Compilation Keybindings Proposal Compilation keybindings proposal May 5, 2016
@phinicota phinicota changed the title Compilation keybindings proposal compilation keybindings proposal May 5, 2016
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Mailling list - Key Bindings stale marked as a stale issue/pr (usually by a bot)
Projects
Mailing list
  
Other
Development

No branches or pull requests

2 participants