You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've never used the JetBrains apps much, and there are no notes in the config that specify which keymap to choose internally in JetBrains so that shortcuts work with the keymap in the Kinto config. I also couldn't find any references about this in the older issues.
I've got a Toshy user that seems to be having problems in PhpStorm and WebStorm and in this case I really don't know what to tell them.
Do you have any idea which internal keymap option the JetBrains keymap in the Kinto config was originally designed to work with?
I have a couple of these apps installed via Snap now on a Fedora system, and they are defaulting to the "GNOME" keymap, but there are several other choices available, including "KDE", "Visual Studio", "VSCode", "Sublime Text", "NetBeans" and a few others.
The text was updated successfully, but these errors were encountered:
Working from mac,win and linux
It's hard for me to have same keymap for all of them
By the way the VSCODE key map in these jetBrains is VSCODE for win
It dont have VSCODE for mac user
@rbreaves
I've never used the JetBrains apps much, and there are no notes in the config that specify which keymap to choose internally in JetBrains so that shortcuts work with the keymap in the Kinto config. I also couldn't find any references about this in the older issues.
I've got a Toshy user that seems to be having problems in PhpStorm and WebStorm and in this case I really don't know what to tell them.
Do you have any idea which internal keymap option the JetBrains keymap in the Kinto config was originally designed to work with?
I have a couple of these apps installed via Snap now on a Fedora system, and they are defaulting to the "GNOME" keymap, but there are several other choices available, including "KDE", "Visual Studio", "VSCode", "Sublime Text", "NetBeans" and a few others.
The text was updated successfully, but these errors were encountered: