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

Add missing keybinding for "Check Code with CheckStyle" command #99

Open
olivarre opened this issue Aug 28, 2018 · 1 comment · May be fixed by #691
Open

Add missing keybinding for "Check Code with CheckStyle" command #99

olivarre opened this issue Aug 28, 2018 · 1 comment · May be fixed by #691
Assignees
Labels

Comments

@olivarre
Copy link

Currently, there is no way to tie this command to a shortcut key because the key binding for it isn't defined in plugin.xml.

I've added the modifications to plugin.xml to bind the "Check Code With CheckStyle" command to a key that is configurable under Eclipse > Preferences > Keys and default it to M1+M2+K (ex: CTRL+ALT+K). This way, users can quickly CheckStyle on the active editor (or files selected in the Package Explorer) without having to use the context menus or rely on building.

I'll commit the changes if this issue is approved.

@lkoe lkoe added the approved label Aug 28, 2018
@infiniator
Copy link

Hi, is it possible to set this up for myself? I am kinda clueless about how to go about doing this, it'll be helpful if you can help with some starter docs to get this done.

@Bananeweizen Bananeweizen self-assigned this Apr 4, 2024
Bananeweizen added a commit to Bananeweizen/eclipse-cs that referenced this issue Apr 4, 2024
This adds a command for the already existing action to run checkstyle on
the selected resources. That way users can invoke the command also via
Ctrl-3 quick assist or via a key binding.

There is no default key binding, as the normal workflow for users is to
rely on the Eclipse builder and to not invoke this command manually.

fixes checkstyle#99
@Bananeweizen Bananeweizen linked a pull request Apr 4, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants