It quickly grew up into a real useful thing, so I decided to implement it into View+
It is really a useful thing.
But current features are insufficient if integrated into V+!
I mean that there must be an opportunity to pass through EOLs also.
E.g. if we have
ABCD ... EOL
QWE ... EOL
AAAZZZ ... EOL,
and search for
CD*AAA
with empty replacement string,
the result must be
ABZZZ ... EOL (1 line!)
In other words, it is not necessary to have a separate tool for line removal in V+, if it is possible now to extend wildcards by letting different string length for search and replacement strings even if * used in search!
It quickly grew up into a real useful thing, so I decided to implement it into View+
It is really a useful thing.
But current features are insufficient if integrated into V+!
I mean that there must be an opportunity to pass through EOLs also.
E.g. if we have
ABCD ... EOL
QWE ... EOL
AAAZZZ ... EOL,
and search for
CD*AAA
with empty replacement string,
the result must be
ABZZZ ... EOL (1 line!)
Leo
I'm not sure I understand your point, Leo!
When talking about empty replacement string do you mean Search&Replace feature in Find+ or Text Line Remover?
Because there is no replacing function in Text Line Remover!?!
Posted: Fri Oct 28, 2005 7:13 pm Post subject: Re: Text Line Remover added to View+
Leo wrote:
In other words, it is not necessary to have a separate tool for line removal in V+, if it is possible now to extend wildcards by letting different string length for search and replacement strings even if * used in search!
Now it's clear what you mean
1) It would be only partially possible to use (*) wildcard in Search&Replace of different length strings! Meaning, only in case that (*) is used within search string, like AB*CDE. If (*) is at the start or at the end of pattern it is impossible to correctly determine the start or the end byte of the found string! Aside problems with handling EOLs in the process!
2) Adding all usefull conditions from Text Line Remover to Find+ dialog would also
produce a total mess! Mission impossible!
So I think it's better to keep them separated until some more fortunate solution found for handling wildcards in Search&Replace!
1. N+ screen is not refreshed after operation completed.
Must refresh it manually - inconvenient
2. Unlike stand-alone version, V+ does not return to main TLR dialog after opearation is finished.
So, when working on some file, one must invoke TLR again and again
3. Neither *string nor something*string do not work in "start of line" mode - reports no lines found (works if "everyware")
1. N+ screen is not refreshed after operation completed.
Must refresh it manually - inconvenient
2. Unlike stand-alone version, V+ does not return to main TLR dialog after opearation is finished.
So, when working on some file, one must invoke TLR again and again
3. Neither *string nor something*string do not work in "start of line" mode - reports no lines found (works if "everyware")
Leo
Points 1) and 2) - cosmetic problem! Shall change it
Point 3)
*string works for me something*string actually works if "Force EOL's" is checked!
These things are very delicate. But I'll fix this
BTW, Search&Replace in Find+ now works with asterisk (*) wildcards used in searched string! So you can replace something*string with something
Also, you can remove something*string
"Incremental" dialog is much improved (more informative).
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Join! (free) 
Profile
Log in to check your private messages
Log in
