[Libreoffice-ux-advise] [Bug 150811] Support flags in Search Commands: whole-word, case-sensitive, regexp

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=150811

--- Comment #6 from Eyal Rozenberg <eyalroz1 at gmx.com> ---
(In reply to Heiko Tietze from comment #3)
> I dislike the idea to make a very simple but efficient interaction complex
> and clunky with very rarely needed functions.

The simple and efficient interaction should not be affected, and even visually
this could made unintrusive. Extreme example: Look at gedit's search box. Or
how CLion's editor pane search has, at the end of the search box, three buttons
which are easy to ignore if you're not looking for them.

> Do you have good use cases?

Maybe, you be the judge.

1. I can't figure out how many spaces LO uses in its menu-to-item separation.
So should I search for "Format/Foo"? "Format / Foo"? "Format /  Foo"? No, I'll
search for regexp "Format */ *Foo".
2. I want to search for a command which has the word Insert, but I don't just
want to match the whole Insert menu. So I'll search for the regexp ".Insert".
3. I remember I saw a widget named the somethingbar. But it wasn't two words,
it was in a single word. So with a regexp, I'd search for "[^ ]bar"; or with a
case-sensitive search, I'd search for "bar" rather than "Bar".
4. I'm searching for a command involving a Style - but not multiple styles.
With a whole-word search, I'll get only the Style results, not "Load styles
from template", nor "table styles" etc.

However, as I consider these examples, I'm noticing the overall number of
commands is... what, around 1000 or so? With that being the case, perhaps just
a simple keyword search limits the result sufficiently.

-- 
You are receiving this mail because:
You are on the CC list for the bug.