RedBearAK / toshy

Keymapper config to make Linux work like a 'Tosh!
https://toshy.app
GNU General Public License v3.0
226 stars 15 forks source link

Shortcuts to nagivate "back" and "forward" in IntelliJ #260

Closed wyuka closed 2 months ago

wyuka commented 2 months ago

Description of the Changes: I have mapped Cmd+[ to alt+shift+left and Cmd+] to alt+shift+right to be able to go back and forward in IntelliJ or other IntelliJ-based IDEs (example CLion or Goland). I have been using this config myself and feel that the community can benefit from it.

Reason for Changes: I have linked the relevant keymaps in IntelliJ source code below for reference.

IntelliJ defaults on MacOS for "Back" and "Forward" are

  1. Back = meta OPEN_BRACKET
  2. Forward = meta CLOSE_BRACKET

meta OPEN_BRACKET translates to C-Left_Brace, and meta CLOSE_BRACKET translates to C-Right_Brace for toshy config. I would like to be able to use these shortcuts on GNOME.

IntelliJ defaults on GNOME for "Back" and "Forward" are

  1. Back = shift alt LEFT
  2. Forward = shift alt RIGHT

Related Issue(s) or PR(s):

Testing Done: Tested on IntelliJ and Goland in GNOME environment.

RedBearAK commented 2 months ago

@wyuka

Your pull request is excellent. Linking to documentation of the original shortcuts, following the contributor instructions. And I think it may be a valid addition, although I don't use IntelliJ apps so I can't really evaluate it myself. If it is useful and matches the macOS shortcuts, it should probably be in there.

Unfortunately there is something about git and GitHub that I obviously haven't understood, which is causing the 168 commits I've made to dev_beta (since the last time I destroyed and re-created it) to want to re-merge themselves back onto dev_beta from your branch, which is probably based on main.

I'm going to try to do a hard reset of dev_beta to clear those out and leave only your commit on this PR. If this doesn't work like I think it will your PR may end up getting automatically deleted by GitHub, and you may need to submit it again. If that is the case, just apply it to the main branch, ignoring the dev_beta instructions.

Sorry about the trouble, if you don't hear from me again. If this works, I'll add another comment.

RedBearAK commented 2 months ago

@wyuka

I did the hard reset, but it looks like it won't automatically remove the unnecessary commits (mine) from this PR.

I don't know how to remove them other than just having you close this PR and submit a new one. This time base it on main, ignoring the instructions about the dev_beta branch. But the excess commits should also be gone if you apply the PR to dev_beta again.

It looks like your fork only has the main branch, so the problem is coming from my side, not yours.

It's a simple PR so I should be able to merge it safely into main.

RedBearAK commented 2 months ago

@wyuka

I created a PR (#270) from your original commit on your branch and submitted and merged it myself with a copy of the original comment here. You are now listed as a contributor on the main page. Thank you for taking the time to submit such a professional pull request. Next time things should work out better.

I'll be closing this since it's redundant now.

RedBearAK commented 2 months ago

Changes have been merged in PR #270.