Rubymine key combinations in Ubuntu Follow
This is an Ubuntu/Gnome specific question. I use Rubymine on Ubuntu 8.10 in Gnome environment. It seems like there are a lot of key combinations that Rubymine uses for which there are Gnome counterparts and therefore when I click the key combination, Gnome takes over. For example, if I click on a class to find its usage using Alt-F7 key combination then Gnome just grabs that window instead of passing it on to Rubymine. I can either use the context menu (which does not have all the choices) or go to the menu bar and manually select the option to get around it. This is rather slow. Is there a way to let Rubymine be the first recipient of the keystrokes before passing it on to Gnome while I am in Rubymine?
Please sign in to leave a comment.
I've faced the same problem on Gnome. Unfortunally there is no way to do this. There are several variants to cope with it:
I've chosen the second one, for example:I think that ability to move windows using keyboard doesn't really make sence and I just disabled corresponding actions in Gnome
"Remap Gnome keybindings or disable some of them in Gnome main menu | System | Preferences | Keyboard shortcuts"
This sounds like a good option. I will go with that since I do not use key bindings in Gnome anyway, I am much more of a command line person
I disabled the Gnome keyboard shortcuts and most of the Rubymine key combinations are working, but the combination for showing usages CTRL-ALT-F7 does not work. I still have to go the menu to activate it. No big deal, you may want to check it out on your Ubuntu machine.
Along the same lines, the Tip of the Day dialog shows that you can Navigate to a related part of the project by selecting the key combination CTRL-ALT-N which displays a pop-up. This is labeled Navigate to Rails and the dialog says that you can find it under Go To | Naviagate To Rails ...
But there is no Navigate To Rails available under Go To. You may want to include it in for the next release
This action is context sencitive, please ensure you are located in controller, model, test etc.