Some shortcuts are not working

[GreyCanis]

JabRef version 5.2 on Windows 10, Ubuntu 20.04.1 and Mac OS Catalina 10.15.7

Some keyboard shortcuts are not working:

• Ctrl + E : open editor of highlighted reference
• Ctrl + Shift + U : create new unpublished
• Ctrl + Shift + R : create new report
• Ctrl + Shift + P : create new proceedings
• Ctrl + Shift + T : create new phdthesis
• Ctrl + Shift + M : create new masterthesis

Steps to reproduce the behavior:

1. Open the JabRef app
2. Open any library
3. Press shortcut on keyboard

[koppor]

@GreyCanis Do you by accident know the last version where it works?

[Siedlerchr]

We removed some default keybindings for them recently

jabref/src/main/java/org/jabref/gui/keyboard/KeyBinding.java

Line 68 in 71ed32e

NEW_MASTERSTHESIS("New mastersthesis", Localization.lang("New mastersthesis"), "", KeyBindingCategory.BIBTEX),

Edit// On Mac Keybindings use cmd instead of control

[koppor]

At the PR #6960 the discussion is included.

[koppor]

@GreyCanis Are all "create new" important for you? #6960 (comment)

We discussed an see that 4 out of the 5 mentioned key bindings lead to an entry not having a DOI. Thus, the DOI fetcher cannot be used. See https://docs.jabref.org/collect/add-entry-using-an-id for that functionality.

As workaround, you can change your key bindings. See https://docs.jabref.org/collect/add-entry-using-an-id.

Did you know that one can change the entry type by clicking on the left in the entry editor on the type label?

We still need a discussion whether we should re-add those key bindings. See that Ctrl+Shift+R was double bound to both new technical report and to fetch entries from shared database. See #6867. I wonder whether you also stumbled on that issue.

[koppor]

@GreyCanis Can you refine your issue with Ctrl+E? It works with the latest build at https://builds.jabref.org/main/

[koppor]

Refs #6403

[lucasreddinger]

Ctrl+Shift+K isn't working for me for the latest portable version on Windows 11. :(

[koppor]

@lucasreddinger We created a seperate issue at #11294. Please follow up there.