Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
I would like to know why are there conflicting shortcuts in the IntelliJ IDEA although they have Predefined keymaps to match the users’ operating system or the previous IDE/text editor.
I would expect IDEA to have 0 shortcut conflicts. This was my initial expectation from JetBrains for these reasons:
- IntelliJ IDEA is closed source. If the community is not allowed to resolve the overlapping shortcuts one would expect to see them resolved by the developing team. IDEA Ultimate is no exception. The same shortcut conflicts are there too. My point being: this is what we’re paying for. This conflict has been around for 2 years now and it’s still problem in my daily use of IDEA on macOS.
- It doesn’t take that much effort to resolve these. Do your research on the f.ex. the OS and remap the shortcut so that the user doesn’t have to.
- JetBrains could always follow the Apple strategy. Windows 11 is doing this already by excluding older chips so they don’t have to put resources into crafting an OS that runs on every potato PC known to mankind. Vice versa more effort would be put into the 8th. gen+ OS development. Same applies here: make the shortcuts so that they don’t overlap with the latest operating systems.
- It sucks to lookup every shortcut only to bind it again because of a conflict.
I’ve tried to look up answers to why are these shortcut conflicts still a thing on a closed-source IDE but without luck. Is it the money? If yes shouldn’t the consumers have a word on what are they paying for? Is it some technical blocker that I’m not aware of? If so why doesn’t JetBrains include the reason in their documentation?