Started with 20 lines of plain text. Clicked on first line and bulleted it (via toolbar 'Bullets On/Off' button). I need to bullet every alternate line. Selected 3rd line of my document, pressed Ctrl+Shift+Y, but nothing happened to my selected line. I looked at the Edit menu and the 3rd option shows "Repeat: Number On/Off Ctrl+Shift+Y", so I selected it, but again it did not bullet my line. I had to select the toolbar 'Bullets On/Off' button, and use this for every alternate line (much slower than using Ctrl+Shift+Y and mouse together).
I can reproduce this behavior using Mac OSX 10.8.2 and LibreOffice Version 4.1.0.0.alpha0+ (Build ID: cad65120c6da901bf9fe33ab16ad22217efed0c) TinderBox: MacOSX-Intel@3-OSX_10.6.0-gcc_4.0.1, Branch:master, Time: 2013-02-21_23:45:08 Thanks for reporting! Kind regards, Joren
Also reproducible using Version 3.6.5.2 (Build ID: 5b93205). I think this problem is inherit from AOO. Therefore I change the version to 3.6.5.2 (=oldest version we can reproduce) right now.
Reproducible with LO 4.4.0.3, Win 8.1
works fine in LibreOffice 3.3.0
Migrating Whiteboard tags to Keywords: (preBibisect) [NinjaEdit]
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Dear Phil, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Confirmed with Linux bibisect43all that the earliest I can test (3.5) displays the same problem as today's 7.2+. It looks like it should work since it knows that a numbering on/off was last done, but it doesn't affect the current paragraph. One workaround for OP is to hold the Ctrl key down while selecting some bits of the paragraphs that he wants to number. Then the toolbar will bullet all of the selected paragraphs in one shot.
*** Bug 134061 has been marked as a duplicate of this bug. ***
bool SfxListUndoAction::CanRepeat(SfxRepeatTarget&r) const { SAL_DEBUG("SfxListUndoAction::CanRepeat checks ["<< nCurUndoAction<<"] actions, and fails if any cannot undo"); for(size_t i=0;i<nCurUndoAction;i++) { if(maUndoActions[i].pAction->CanRepeat(r)) return false; } return true; } It passes for INSNUM, INSATR, and RESETATR, but not NUMRULE_CREATE, and thus cancels the repeat. So I tested what happens if you try to repeat the SECOND manual numbering instead of the FIRST one, and that works fine, since it isn't creating a new numbering rule. What about if you apply a pre-defined style? That doesn't work at all (but it does work for a paragraph style...). [In this case (SwUndoId::EMPTY == rSh.GetRepeatInfo(nullptr)), so probably a lot of basic plumbing is missing.]
Proposed fix at https://gerrit.libreoffice.org/c/core/+/119201 tdf#60632: sw: Allow SID_REPEAT even if NUMRULE_CREATE
(In reply to Justin L from comment #11) > Proposed fix at https://gerrit.libreoffice.org/c/core/+/119201 tdf#60632: > sw: Allow SID_REPEAT even if NUMRULE_CREATE I abandoned this hack since it is not a clean, neat, or tidy solution.
Dear Phil, 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