Bug 143737 - Tools>Customize>keyboard>numbering assigned to a shortcut does nothing
Summary: Tools>Customize>keyboard>numbering assigned to a shortcut does nothing
Status: RESOLVED DUPLICATE of bug 126464
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.0.2 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks: Shortcuts-Accelerators
  Show dependency treegraph
 
Reported: 2021-08-05 01:04 UTC by TorrAB
Modified: 2021-08-28 14:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description TorrAB 2021-08-05 01:04:01 UTC
Description:
Tools>Customize>keyboard>numbering; assign ~^n to numbering on/off
Put cursor on a numbered paragraph, hit ~^n; nothing happens.

Version: 7.2.0.2 (x64) / LibreOffice Community
Build ID: 614be4f5c67816389257027dc5e56c801a547089
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: en-CA (en_US); UI: en-US
Calc: CL

Steps to Reproduce:
1.Tools>Customize>keyboard>numbering; assign ~^n to Numbering on/off 
2.Put cursor on a numbered paragraph, hit ~^n
3.

Actual Results:
nothing happens.

Expected Results:
number should go


Reproducible: Always


User Profile Reset: No



Additional Info:
none
Comment 1 Dieter 2021-08-20 08:33:47 UTC
Not ure for 100%, what ~^n is, but I assigned ALT+n to Numbering On/Off command an I confirm, that nothing happens. It also fails with other shortcuts. I also don't know the differnece between that command and F12 (ordered list).

So I change status to NEW, but add design-team for double-check.
Comment 2 Heiko Tietze 2021-08-20 09:53:50 UTC
No volunteer so far on the easyhack ;-(

*** This bug has been marked as a duplicate of bug 126464 ***
Comment 3 Dieter 2021-08-20 11:18:01 UTC
(In reply to Heiko Tietze from comment #2)
> *** This bug has been marked as a duplicate of bug 126464 ***

BTW: I havent't searched within the meta bug UNO-Command-New, because this bug is not about new a command. So does it make sense to rename meta bug 86899 to "UNO-Command bugs and enhancements" or something like that?
Comment 4 Heiko Tietze 2021-08-23 07:47:30 UTC
(In reply to Dieter from comment #3)
> BTW: I havent't searched within the meta bug UNO-Command-New, because this
> bug is not about new a command. So does it make sense to rename meta bug
> 86899 to "UNO-Command bugs and enhancements" or something like that?

True. We have

bug 86899 	[META] Requests for the addition of UNO commands  
bug 141420 	[META] UNO Object Inspector - Development tools  
bug 115596 	[META] Labels of UNO commands bugs and enhancements  
bug 117710 	[META] UNO API issues  

So perhaps we should create another META for issues with UNO commands or merge those into bug 115596 and rename this one.
Comment 5 Dieter 2021-08-28 14:54:51 UTC
(In reply to Heiko Tietze from comment #4)
> True. We have
> 
> bug 86899 	[META] Requests for the addition of UNO commands  
> bug 141420 	[META] UNO Object Inspector - Development tools  
> bug 115596 	[META] Labels of UNO commands bugs and enhancements  
> bug 117710 	[META] UNO API issues  
> 
> So perhaps we should create another META for issues with UNO commands or
> merge those into bug 115596 and rename this one.

Thanks for the overview. Bug 117710 is still a meta-bug for bug 115596 and bug 86899. So I just added bug 141420. Since I'm not a developer I don't know, if "UNO API" is the same as "UNO command". So for people like me it would be helpful to use consistent lables (if possible).