Bug 64444 - ACCESSIBILITY: Change the defaut redo hotkey on *nix builds to the de-facto stananrd of CTRL+SHIFT+Z
Summary: ACCESSIBILITY: Change the defaut redo hotkey on *nix builds to the de-facto s...
Status: RESOLVED DUPLICATE of bug 32368
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected) rc
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2013-05-10 20:30 UTC by Hugo Osvaldo Barrera
Modified: 2013-05-10 20:34 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Hugo Osvaldo Barrera 2013-05-10 20:30:09 UTC
Problem description: 

The default hotkey for redo is not the defacto standard for every OS. As an ocasional user of libreoffice, while editing a document I found I could not redo any thing with Ctrl+Shift+Z. After looking at the menu, I found out the redo key was Ctrl+Y, which struck me as rather odd.

After some (really short) research, I found out that Ctrl+Y is generally the default for redoing in microsoft software, however, Ctrl+Shift+Z is the defacto standard for *nix. (Cmd+Shift+Z is the default on Mac).

It would be nice for the *nix builds of libreoffice to have the same default hotkeys as the rest of the desktop.
While many would suggest I reconfigure libreoffice, I belive most users would be more confortable if the default hotkeys matched the one used by all other applications on their OS of choice (otherwise, libreoffice actually behaves rather "alien").

Steps to reproduce:
1. Type some text
2. Delete it
3. Press the undo key combination used by all other software in that particular OS.

Current behavior:
 Deletion should be undone.

Expected behavior:
 Nothing happens.

Operating System: Linux (Other)
Version: rc
Comment 1 Jorendc 2013-05-10 20:33:12 UTC
I agree completely to that.

Thanks for reporting! I'll take it (but first ask UX-advice to be sure).

Kind regards,
Comment 2 Jorendc 2013-05-10 20:34:48 UTC

*** This bug has been marked as a duplicate of bug 32368 ***