Bug 144560 - <Command>+R not customizable in LO Writer
Summary: <Command>+R not customizable in LO Writer
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
7.1.5.2 release
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Mac
  Show dependency treegraph
 
Reported: 2021-09-16 21:03 UTC by Alexis
Modified: 2025-03-24 03:10 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Image file showing superficially assigned shortcut (400.76 KB, image/png)
2023-03-24 19:41 UTC, Alexis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexis 2021-09-16 21:03:02 UTC
Expected behavior: Assigning <COMMAND>+R (Apple's command key and then the letter "R" key at the same time) to a working macro in LO 7.1.5.2 (for macOS 10.15.7) should trigger the macro when <COMMAND>-R is pressed.

Actual behavior: paragraph is aligned right.

Steps to reproduce:

1. Open a new Writer document.

2. Record a macro (e.g., to change the color of selected text to Red), save as "Red", and confirm that it works by selecting some text (e.g., black text) and running macro Red. Watch the text turn red. Yay.

3. Customize <COMMAND>+R to LibreOffice Macros > MyMacros > Standard > Module1 > Red using the Customize dialog. For extra giggles, be sure to customize Right (the RightPara one) to something else, like <COMMAND>+].

4. Select some text and type <COMMAND>+R: watch the paragraph in which the selected text is located shift to the right and NOT change to red-color text.

5. Tear your hair out for a bit. Recheck your various settings. Weep maybe. Then resign yourself to the fact that <COMMAND>-R is hard coded to RightPAra in LO 7.1.5.2


Comments 
(1) macOS 10.15.7 does NOT reserve <COMMAND>+R to this behavior.

(2) Above behavior is reproduced in LO 7.1.6.2.

(3) It IS possible to assign macro "Red" to another key, such as <CTRL>+R.

(4) I would love a list of all hard-coded keyboard shortcuts in LO, and for the customize dialog to automatically gray these out, or otherwise indicate that their settings will not be honored.
Comment 1 Alexis 2021-10-10 16:37:50 UTC
Bug recapitulated on macos Big Sur.
Comment 2 eisa01 2022-02-05 15:32:44 UTC
Was going to test this, but recording macros require Java which is not supported on ARM?
Comment 3 Alexis 2022-02-06 05:13:25 UTC
(In reply to eisa01 from comment #2)
> Was going to test this, but recording macros require Java which is not
> supported on ARM?

I am not sure what you are trying to communicate: my bug report is specific to macOS, and my Apple machine has an Intel processor, not Arm.
Comment 4 eisa01 2023-03-24 19:17:09 UTC
This is present

Version: 7.4.6.2 / LibreOffice Community
Build ID: 5b1f5509c2decdade7fda905e3e1429a67acd63d
CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 5 Alexis 2023-03-24 19:41:13 UTC
Created attachment 186198 [details]
Image file showing superficially assigned shortcut
Comment 6 Alexis 2023-03-24 19:41:24 UTC
Bug is also present in LO 7.4.6.2 on macOS Monterey.

Additional comment: other keyboard shortcuts are apparently also hard coded. For example, I want to assign Writer > File > Export As… > Export Directly as PDF to <COMMAND>+<E>, but after doing so in Writer > Tools > Customize (see the attached image where the menu shows the shortcut 'assigned' as described), when I type <COMMAND>+<E> I get the default behavior of Justify Paragraph Centered.

Shortcut customization for macOS is somewhat broken, with undocumented hard-coded shortcuts (which are not hard-coded by the OS).
Comment 7 QA Administrators 2025-03-24 03:10:40 UTC
Dear Alexis,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug