NISUS Archives

May 2010

NISUS@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0 (Apple Message framework v1078)
Sender:
A discussion list for Nisus & NisusWriter <[log in to unmask]>
Date:
Sat, 1 May 2010 21:41:50 +0900
Reply-To:
Subject:
From:
Content-Transfer-Encoding:
quoted-printable
In-Reply-To:
Content-Type:
text/plain; charset=us-ascii
Comments:
Parts/Attachments:
text/plain (34 lines)
On May 1, 2010, at 3:23 PM, Andrus wrote:

> Meanwhile, NWP 1.3 is irritating me.  Maybe I need to learn how to cope with it.  Is it just me?

This is a bug. I reproduced the problem with NWP 1.4.1 in OS X 10.6.3 and just sent a feedback to them together with your message.


> When I paste the find string in (if already set to PowerFind Pro) it works fine.
> Then I save the find string and give it a name (GremlinGrabber), thinking all will be fine in the future.
> 
> However, since my normal mode is plain PowerFind, it ends up in that setting, and even if I first set to PowerFind Pro before I select the GremlinGrabber "saved string", it converts it with the extra back-slashes as it does when switching from plain PowerFind to Pro.  Thus, I have to copy the find string while in the PowerFind mode, switch to Pro, and then paste in the find string.
> 
> I should think if I save a PowerFind Pro find string, it would be able to set itself properly whenever I select that find string.  I suppose this is a manifestation of the deficiency in NWP that it does not properly or fully convert between the plain and Pro settings?

In the feedback, I asked them to make the regex engine understand a special directive force-setting the find mode. E.g.

	(?E)[\x00-\x1F\x7F-\x9F&&[^\t\n\f]]  # E for PowerFind Pro

I don't know if they will add this or something alike in a near future. Perhaps they have a better idea, of course.

Anyway, as a work around... how many PowerFind Pro saved expressions do you have? If they are not so many, perhaps it would not be so hard to use macros like below instead of them. Not elegant but macros have an advantage that you can assign shortcuts to them.


$findExpression = Cast to String '[\x00-\x1F\x7F-\x9F&&[^\t\n\f]]'
$replaceExpression = Read Replace Expression  # Store Replace Expression

Find and Replace '', '', 'E*!'  # clear Find and Replace expressions and switch to PowerFind Pro

Write Find Expression $findExpression  # set Find Expression
Write Replace Expression $replaceExpression  # Restore Replace Expression


Kino

ATOM RSS1 RSS2