In article <[email protected]>,
   Gene Young <[email protected]> wrote:
> On 2/1/2011 4:24 AM, Brian Barker wrote:
> > At 08:01 31/01/2011 -0500, Gene Young wrote:
> >> On 1/31/2011 1:08 AM, John Jason Jordan wrote:
> >>> On Mon, 31 Jan 2011 04:10:49 +0000
> >>> Brian Barker<[email protected]> dijo:
> >>
> >>>
> >>> Hmm. You're right. I never tried it until just now, but it doesn't
> >>> work with spaces.
> >>
> >> To search and replace spaces you must use regular expressions and use
> >> [\x0009 ] as the search term for a space and a regular space
> >> (spacebar) for the replace with term.
> >> ie;
> >>
> >> Find; .[\x0009 ][\x0009 ]
> >> Replace with: .
> >>
> >> Note: There is a space after the dot in Replace with.
> >>
> >> This works as needed. (I tested it.)
> >
> > Sorry, but this is somewhat confused.
> >
> > First, I didn't write any of the above. Do please take care when you
> > edit messages that you do not misattribute what was written.
> >
> > Second, the comment above that something didn't work with spaces was
> > referring to AutoCorrect, not Find & Replace. Finding or editing such
> > multiple spaces using Find & Replace had already been discussed
> > successfully: that wasn't what didn't work.
> >
> > Third, your suggestion that spaces cannot be used naturally in the
> > "Search for" field in Find & Replace is simply wrong: they can. There is
> > no need for your complicated workaround, in fact.
> >
> > Brian Barker
> >
> >

> First I was merely describing how to search for and replace the (Dot 
> Space Space) string with a (DOT Space) string.  I wasn't 
> "misattributing" any thing to anyone.

> Second I tried searching and replacing with the actual period and space 
> characters.  It DIDN'T work.

> Third when I see someting that indicates that you have officially been 
> appointed list cop I MIGHT pay attention to you , but I doubt it.

> Until then, PLONK.

Hmm. 

1) Brian did have a legitimate complaint. Your post did suggest that he had
said something that he hadn't said. But then I assume you can see that from
(I quote):
        
> >>> Brian Barker<[email protected]> dijo:
> >>
> >>>
> >>> Hmm. You're right. I never tried it until just now, but it doesn't
> >>> work with spaces.

(Yes, I know if you take the trouble to count the '>'s' you can see that he
didn't say what appears below his name, but then why leave his name in at
all when you have cut out what he actually did say?)

2) Searching for actual period and space characters certainly does work for
me (OOo 3.2, Windows XP) (just checked to make sure, but I use it all the
time). Perhaps you had 'Whole word only' checked in the search dialogue,
which does appear to prevent it from working?

3) Brian Barker may not be appointed 'list cop', but he is probably the
single most helpful poster on this list - he rarely gets it wrong. So the
wisdom of 'PLONKING' him is debatable. Your loss though :-(

R.

-- 

  Richard Travers 
  [email protected]
  Truro, Cornwall
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to