In the Help file, in the list of regular expressions, this appears: "* Finds zero or more of the characters in front of the '*'. For example, 'Ab*c' finds 'Ac', 'Abc', 'Abbc', 'Abbbc', and so on." That, because it says "zero or more", for the example, would also find "c", thus it would find everything. But that's not the actual behavior when I tested. Similarly, it says, "? Finds zero or one of the characters in front of the '?'. For example, 'Texts?' finds 'Text' and 'Texts' and 'x(ab|c)?y' finds 'xy', 'xaby', or 'xcy'." That means that "Texts?" will find all instances of "?". Clearer wordings are needed.
(In reply to Nick Levinson from comment #0) > In the Help file, in the list of regular expressions, this appears: "* Finds > zero or more of the characters in front of the '*'. For example, 'Ab*c' > finds 'Ac', 'Abc', 'Abbc', 'Abbbc', and so on." That, because it says "zero > or more", for the example, would also find "c", thus it would find > everything. But that's not the actual behavior when I tested. > > Similarly, it says, "? Finds zero or one of the characters in front of the > '?'. For example, 'Texts?' finds 'Text' and 'Texts' and 'x(ab|c)?y' finds > 'xy', 'xaby', or 'xcy'." That means that "Texts?" will find all instances of > "?". > > Clearer wordings are needed. * and ? are not treated like characters, but like conditions. Escaping \? would find the character '?'. Also, the 'c' when it appears in the expression is treated like part of the condition to "look at what character is allowed to appear immediately before 'c'". What is your proposal for the revised wording? Disclosure: I'm not particularly skilled with regexes and usually have to stare at them with my eyes glazed over for long periods of time to understand anything.
That's exactly why clarification would help: if you know something about it and you still have to stare at it to figure out what it means, ordinary public users would be totally lost. The Help says this about regex: "Allows you to use wildcards in your search." Geeks don't need much, but a friendlier treatment is needed for ordinary Earthlings. Here's a first draft: "Regexes are for complex searches that can't be done in simpler ways. They include wildcards (characters you use when you're not sure exactly which characters you need to find), ways of searching for characters that can't be typed directly (like tabs and paragraph endings), and characters in certain positions (like at a line beginning)." Maybe someone else can improve on that draft. I know the asterisk and question mark are not literal search terms unless escaped, but the phrasing in Help was not quite what was happening in applying regex. The "c" is also about phrasing in Help. When I recently went back to the Help list, I discovered that the two wildcards are not used quite as some other software uses them, and that might add to the potential confusion. I'm not a great expert on regex and would prefer that someone else clarify the Help.
(In reply to Nick Levinson from comment #2) > That's exactly why clarification would help: if you know something about it > and you still have to stare at it to figure out what it means, ordinary > public users would be totally lost. I was referring to using regex in any editor or programming language and I believe this blank staring is the effect they have on all, who don't use them regularly (pun intended) or never invested a substantial amount of time to learning them :) So the target group is certainly not ordinary users, but power users. I'll set to NEW in any case and change component to Documentation.
** 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.5 or 5.2.1 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-20160920
Pierre F committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/969dc658744688aa9e1dc64611a327399d078462 less tautological and more reader friendly wording (tdf#91336)
Note: The list document was already fixed, refering now to "regular expression term immediately preceding" There's also a related otpic linked as "Using Regular Expressions in Text Searches"