Mime-Version: |
1.0 (Apple Message framework v753.1) |
Sender: |
|
Date: |
Sat, 6 Aug 2011 14:57:30 -0600 |
Reply-To: |
|
Subject: |
|
From: |
|
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
<a06110406ca63529dfdf7@[10.0.1.21]> |
Content-Type: |
text/plain; charset=US-ASCII; delsp=yes; format=flowed |
Comments: |
|
Parts/Attachments: |
|
|
Have you tried quitting Nisus and then relaunch?
I just cranked up Nisus 1.3 to see what happens, and it couldn't find
anything I asked it. Then somehow it would "Find All" but didn't
show them selected! (reported three hits and copy got them, or bksp
killed them all.
So I was about to give up and then relaunched and it worked normal.
So maybe a relaunch would be worth trying...
Now I'm frustrated too, with erratic behaviour! :-)
Incidentally, upon a lark I checked, and after the relaunch, the back-
slashes work as you'd expect in PowerFind Pro.
Ben Andrus
__________________________________________________
On 2011 Aug 6, Sat, at 2:22 pm, Robert B. Waltz wrote:
> On 8/6/11, Andrus wrote:
>
>> Can you get any help by recreating the function in Powerfind, then
>> when it works, switch it to PowerFind Pro and see what Nisus
>> creates in the Pro code?
>
> I tried that. And the PowerFind to PowerFindPro conversion gets it
> wrong -- it converts ..(1plus) to ..+ (or something to that
> effect). That latter string when placed in a macro does exactly
> what is expected of it: it selects the whole document. The question
> is what to use instead of \.\., which ALSO selects the whole
> document. :-(
> --
> Bob Waltz
> [log in to unmask]
>
> "The one thing we learn from history --
> is that no one ever learns from history."
|
|
|