I wanted to quickly search for hotkeys I haven’t committed to memory. Here are v9.0.2 hotkey/shortcut definitions massaged from my …\user.hotkeys file converted to table (fixed column) format using several common file types. I used only the Ctrl keyword for Windows and Linux, which may be the only keyboard translation needed for Apple users. All files are easily searchable using the associated viewers and editors. Since these are ‘source’ files you can edit them for your own needs.
Does this seem a bit OCD? Perhaps, but this is an advantage for a technical person! I l appreciate easy-to-use and reasonably complete documentation. However, as always, YMMV.
In: … / Preferences / Preferences / Hotkeys you also have an overview of all hotkeys directly in KiCad itself. And you can search though them, sort by different columns and of course also assign key combinations to functions that don’t have a hotkey assigned yet. I don’t really understand why putting these hotkeys into some other file format would be advantageous.
A few years ago someone made a cheatsheet for KiCad. A single A4 page with an overview of the most used hotkeys and that you can print out as an aid for learning KiCad. I can see that being useful for beginners, but an 18 page printout of all keys?
All the lists of hotkeys I have found made “years ago” are badly incomplete and outdated. They even conflict with each other probably due to them being from different versions. They don’t even state from which version they refer.
Viewing a printed hand-picked subset of the hotkeys is more convenient than switching windows unless you have multiple monitors. In either case glancing from one list to another seems better than throwing up a temporary window which covers up the work in progress.
These files may be marked up and notes added as you please. The built-in hotkeys list can’t be edited or printed, AFAIK.
