Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

Hi :)
Questions are often vague.  Even where they are clear it's often
obvious the person asking the question really needs to know something
they had no idea how to ask about.  Either a shortcut route or a
"don't even try it , do this instead".  Often 3 different people can
read the same question and have 5 different ideas about how best to
answer it.

It's pretty rare for anyone to acknowledge when a question has been
solved and a "Perfect" is almost unheard of even though many of you do
give excellent answers.
Regards from
Tom :)

On 8 November 2013 06:32, Brian Barker <> wrote:
At 08:24 28/10/2013 +0100, Miroslaw Zalewski wrote:

Dnia 2013-10-28, o godz. 00:24:38 Brian Barker napisal(a):

That's because your original question was not at all clear!  (You owe it
to correspondents not to waste their time.)

I disagree. The question was perfectly clear.

Thanks for this - but I'm afraid not.  The original question was "Does the
Find & Replace dialog box allow backreferences in the 'Replace with' field?
(I'm having trouble getting it to work.)".  No-one was able to answer it
until the original questioner explained himself.  Were you perhaps instead
reading his revised message?

"Backreference" is one of basic terms in regular expressions theory. If
you ask about regexpes, you may safely assume that your peers knows what
"backreference" means.

You've latched onto "backreference" as if not understanding that was the
substance of my comment.  But I didn't mention that.  Instead, the problem
was that the questioner initially did not explain what problem he had with
backreferences.  Indeed, it transpired that his problem was that he didn't
need backreferences at all.  Backreferences are how you refer back to a
matched string within the pattern itself, not how you refer to the same
thing in the replacement string.  (See Wikipedia: "grouping subexpressions
with parentheses and recalling the value they match *in the same expression*
(backreferences)" (my emphasis).)  The user's problem was that he was
erroneously using the syntax for backreferences in an attempt to create a
reference in the replacement string.

Statement in parentheses applies to both sides - the one asking the
question as well as people who answer it.

Well, that's certainly true.  But I cannot see how you can suggest (as you
clearly were) that I was wasting the questioner's time.  Once he identified
his problem, I provided an explanation which he described as "Perfect".

Brian Barker

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.