No keyboard shortcuts—all are disabled?

[marty39]

I've been using Gimp for years on a Mac, using a few keyboard shortcuts. I keep it up to date, now using Gimp 3.0.2. All the keyboard shortcuts I used to use in Gimp 2.x are disabled. I deleted shortcutsrc to create the default shortcutsrc, and all the shortcuts are commented out.

Why? What happened? How can I get back the keyboard shortcuts I used to use in Gimp 2.x?

Of course I renamed the default shortcutsrc and brought back the shortcutsrc from the Trash folder so I could have the few shortcuts I created myself. But I'd like to have the whole set.

[rich2005]

(05-13-2025, 02:54 PM)marty39 Wrote: I've been using Gimp for years on a Mac, using a few keyboard shortcuts. I keep it up to date, now using Gimp 3.0.2. All the keyboard shortcuts I used to use in Gimp 2.x are disabled. I deleted shortcutsrc to create the default shortcutsrc, and all the shortcuts are commented out.

Why? What happened? How can I get back the keyboard shortcuts I used to use in Gimp 2.x?

Of course I renamed the default shortcutsrc and brought back the shortcutsrc from the Trash folder so I could have the few shortcuts I created myself. But I'd like to have the whole set.

The format for recording shortcuts has changed between Gimp 2.10 and Gimp 3.0 and the file is renamed as well. Gimp 2.10 = menurc Gimp 3.0 = shortcutsrc

As an example, one I always set to remove all guides.
menurc
(gtk_accel_path "<Actions>/plug-in/script-fu-guides-remove" "g")
shortcutsrc
(action "script-fu-guides-remove" "g")

The old syntax is not going to work in Gimp 3.0 It might be possible to write a script to convert between formats but just bite-the-bullet and do it manually.

Why all the # starting the default settings, I do not know. AFAIK (by use) it does not disable the shortcut.

[programmer_ceds]

(05-14-2025, 07:33 AM)rich2005 Wrote:

(05-13-2025, 02:54 PM)marty39 Wrote: I've been using Gimp for years on a Mac, using a few keyboard shortcuts. I keep it up to date, now using Gimp 3.0.2. All the keyboard shortcuts I used to use in Gimp 2.x are disabled. I deleted shortcutsrc to create the default shortcutsrc, and all the shortcuts are commented out.

Why? What happened? How can I get back the keyboard shortcuts I used to use in Gimp 2.x?

Of course I renamed the default shortcutsrc and brought back the shortcutsrc from the Trash folder so I could have the few shortcuts I created myself. But I'd like to have the whole set.

The format for recording shortcuts has changed between Gimp 2.10 and Gimp 3.0 and the file is renamed as well. Gimp 2.10 = menurc  Gimp 3.0 = shortcutsrc

As an example, one I always set to remove all guides.
menurc
(gtk_accel_path "<Actions>/plug-in/script-fu-guides-remove" "g")
shortcutsrc
(action "script-fu-guides-remove" "g")

The old syntax is not going to work in Gimp 3.0 It might be possible to write a script to convert between formats but just bite-the-bullet and do it manually.

Why all the # starting the default settings, I do not know. AFAIK (by use) it does not disable the shortcut.

Anything following the # is treated as a comment. So the lines starting with # and then the default settings are simply showing what the defaults are.

[rich2005]

(05-14-2025, 09:37 AM)programmer_ceds Wrote: Anything following the # is treated as a comment. So the lines starting with # and then the default settings are simply showing what the defaults are.

Does that mean that the defaults are in the main Gimp code somewhere. ? (edit- must be not a default file in etc/gimp)
So for example my, remove-all-guides G , does not start with a # Is that just an over-ride of existing state ?
Is it possible for example to delete all the entries starting with # and have a shorcutsrc file consisting of just your own settings ?

Edit: Answer my own question - a quick try and a one line shortcutsrc file containing (action "script-fu-guides-remove" "g") seems to work.
So you might be able to take a menurc file and a bit of terminal SED or text find-replace and make a Gimp 3 file.

[marty39]

(05-14-2025, 09:37 AM)programmer_ceds Wrote:

(05-14-2025, 07:33 AM)rich2005 Wrote:

(05-13-2025, 02:54 PM)marty39 Wrote: I've been using Gimp for years on a Mac, using a few keyboard shortcuts. I keep it up to date, now using Gimp 3.0.2. All the keyboard shortcuts I used to use in Gimp 2.x are disabled. I deleted shortcutsrc to create the default shortcutsrc, and all the shortcuts are commented out.

Why? What happened? How can I get back the keyboard shortcuts I used to use in Gimp 2.x?

Of course I renamed the default shortcutsrc and brought back the shortcutsrc from the Trash folder so I could have the few shortcuts I created myself. But I'd like to have the whole set.

The format for recording shortcuts has changed between Gimp 2.10 and Gimp 3.0 and the file is renamed as well. Gimp 2.10 = menurc  Gimp 3.0 = shortcutsrc

As an example, one I always set to remove all guides.
menurc
(gtk_accel_path "<Actions>/plug-in/script-fu-guides-remove" "g")
shortcutsrc
(action "script-fu-guides-remove" "g")

The old syntax is not going to work in Gimp 3.0 It might be possible to write a script to convert between formats but just bite-the-bullet and do it manually.

Why all the # starting the default settings, I do not know. AFAIK (by use) it does not disable the shortcut.

Anything following the # is treated as a comment. So the lines starting with # and then the default settings are simply showing what the defaults are.

No. In the default shortcutsrc, not only are all lines commented out, but only a few of them show any keystroke information. Like this:

# (action "script-fu-guide-new")
# (action "context-palette-foreground-first")
# (action "view-zoom-1-4" "numbersign" "<Shift>KP_3")
# (action "view-snap-to-canvas")
# (action "filters-bump-map")

 In my actual working shortcutsrc, some of the actions—I suppose the ones I used from the menu—are uncommented, but most of them still don't show any keystroke info, while the actions I assigned are uncommented and show the keystroke I assigned. Like this:

# (action "filters-recent-10")
(action "view-zoom-out" "KP_Subtract")
# (action "filters-gegl-fractal-explorer")
# (action "tools-opacity-decrease-skip" "<Primary>less")
# (action "view-scroll-right")
(action "view-zoom-revert")
# (action "filters-diffraction-patterns")
(action "tools-align")
# (action "windows-show-display-previous" "<Shift><Alt>Tab" "Back")

The corresponding portion of the default shortcutsrc is:

# (action "filters-recent-10")
# (action "view-zoom-out" "minus" "KP_Subtract" "ZoomOut")
# (action "filters-gegl-fractal-explorer")
# (action "tools-opacity-decrease-skip" "<Primary>less")
# (action "view-scroll-right")
# (action "view-zoom-revert" "grave")
# (action "filters-diffraction-patterns")
# (action "tools-align" "q")
# (action "windows-show-display-previous" "<Shift><Alt>Tab" "Back")

Puzzle: The default shortcutsrc shows three keys that could activate action "view-zoom-out," but I didn't see any way within the Gimp app to make them work. All I could do was specify one keystroke for it.

[rich2005]

Well, an uncommented line will supercede a commented line and overrule the default.

# (action "view-zoom-out" "minus" "KP_Subtract" "ZoomOut")
is minus key or keypad minus key (which might be embedded in a laptop) or (I think) the mouse

as a test try
(action "view-zoom-out" "a" "b" "c")
and the a b and c keys zoom out (at least they do here)

[marty39]

OK, one command in MacVim uncommented all the actions in the default shortcutsrc, so now I have all the default shortcuts. Then I put in a couple of my own using the GIMP > Keyboard Shortcuts window so I could see if they would override a default; one would so I used a different key.

I would still like to know why I got Gimp 3.0 with all the keyboard shortcuts disabled.

[rich2005]

I did this earlier then skipped it.  It shows what happens when you edit a key short cut. As you say the shortcuts are disabled so the defaults apply.

When changed the the existing shortcut is uncommented and the action is removed, that key no longer works.
Then the new action is added to the new shortcut.

I suppose it is this way to avoid conflicts.