^13 code for finding paragraph marks is broken!

[kevinobrien3]

I have a brand new Mac OS X, version 10.3.9.
In Microsoft Word, when I try to find paragraph marks with ^13 when
wildcards is checked, it says the pattern match expression is not
vaild.
Without wildcards checked, ^13 works fine. And all other codes work
fine with
or without wildards checked.
Does anyone know how I can search on paragraph marks in my version of
Word
with wildcards checked?

PS - strangely, ^10 with wildcards checked returns a message 'not
found', which is equally unhelpful, alas.

 

[matt neuburg]

I have a brand new Mac OS X, version 10.3.9.
In Microsoft Word, when I try to find paragraph marks with ^13 when
wildcards is checked, it says the pattern match expression is not
vaild.

That's because it isn't valid when wildcards is checked.

Without wildcards checked, ^13 works fine.

That's because it is valid when wildcards isn't checked.

Does anyone know how I can search on paragraph marks in my version of
Word
with wildcards checked?

Certainly: use \n. Gosh, why didn't you just ask that to start with? m.

 

[Elliott Roper]

Certainly: use \n. Gosh, why didn't you just ask that to start with? m.

Oo er! Neato. Where is that documented? Has she got any other friends
not listed in the wildcard help?

I notice that although ^p stops working with wildcards on, ^t is still
OK. It's all a bit inconsistent isn't it?

 

[Russs]

Oo er! Neato. Where is that documented? Has she got any other friends
not listed in the wildcard help?

I notice that although ^p stops working with wildcards on, ^t is still
OK. It's all a bit inconsistent isn't it?

^13 does seem to be 'broken' on the Mac version of Word since this link:
http://www.gmayor.com/replace_using_wildcards.htm
implies that using (*^13)\1 in the find textbox to locate duplicate lines
does need wildcards turned on to work in a Windows based version of Word.

And I think that \n does work for finding a 'newline' on the Mac but not on
a Windows machine, because I tried using a macro I copied from a Mac and ran
at work on a Windows machine to find a newline or paragraph with no success.

 

[matt neuburg]

^13 does seem to be 'broken' on the Mac version of Word since this link:
http://www.gmayor.com/replace_using_wildcards.htm
implies that using (*^13)\1 in the find textbox to locate duplicate lines
does need wildcards turned on to work in a Windows based version of Word.

Indeed, the online documentation specifically says that ^13 should work.
"Documentation? We don't need no stinkin' documentation!" m.