Re: [WebDNA] can webdna's [grep] find and replace ONLY the literal "+" char?
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 109017
interpreted = N
texte = > [grep search=3D[[url]+[/url]]&replace=3Dsomething]Wow, cool! You cracked one that I figured was never going to be =cracked) :-)> The URL's seem to work in many literal cases for some reason... =spaces, returns, etc..here ^^^ you are referring to using [url] wrappers around Webdna =tag/context params? I have been under the impression that SmithMicro =(or even PCS before them) years ago decided that [url] was their =official chosen method of escaping any and all tag/context params, and I =have been using it that way for years in many different situations. =Anyway, indeed, as you say, it works. IOW, I am not surprised.. and I =even had tried using [url]. But what I did not think of, and am =surprised by, is that it works used *inside* a grep character class. I =mean, an [url] wrapper like this makes sense in the context of my/our =understanding described in this paragraph:[grep search=3D[url][+][/url]&replace=3Dsomething]...but does not work.But AFAICT this:[grep search=3D[[url]+[/url]]&replace=3Dsomething]...*should* be finding/matching any character that is just/only one of =these three chars:%2BIf Webdna had any development cycles, I would ask those techs, should we =rely on "[grep search=3D[[url]+[/url]]..." behaving as it does today? =I'd rather it was fixed, if I was still attached.=20But something predictable (for now) is better than nothing.. thanks =:-)-Govinda=
Associated Messages, from the most recent to the oldest:
> [grep search=3D[
[url]+[/url]]&replace=3Dsomething]Wow, cool! You cracked one that I figured was never going to be =cracked) :-)> The URL's seem to work in many literal cases for some reason... =spaces, returns, etc..here ^^^ you are referring to using
[url] wrappers around Webdna =tag/context params? I have been under the impression that SmithMicro =(or even PCS before them) years ago decided that
[url] was their =official chosen method of escaping any and all tag/context params, and I =have been using it that way for years in many different situations. =Anyway, indeed, as you say, it works. IOW, I am not surprised.. and I =even had tried using
[url]. But what I did not think of, and am =surprised by, is that it works used *inside* a grep character class. I =mean, an
[url] wrapper like this makes sense in the context of my/our =understanding described in this paragraph:[grep search=3D
[url][+][/url]&replace=3Dsomething]...but does not work.But AFAICT this:[grep search=3D[
[url]+[/url]]&replace=3Dsomething]...*should* be finding/matching any character that is just/only one of =these three chars:%2BIf Webdna had any development cycles, I would ask those techs, should we =rely on "[grep search=3D[
[url]+[/url]]..." behaving as it does today? =I'd rather it was fixed, if I was still attached.=20But something predictable (for now) is better than nothing.. thanks =:-)-Govinda=
Govinda
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Pref settings? (1998)
Webcat table size. (2001)
MacWEEK article help needed (1996)
Too many lines too add in one go (2003)
Custom Shipping Charges (1997)
multi-paragraph fields (1997)
Date search bug (1998)
Fufillment e-mail? (1998)
Changes to the List (1997)
[OT] ISP Windows program (2005)
Banner ads (2000)
[WebDNA] max number of searches and lookups on a page (2016)
Keyword search (2004)
Store Builder, technical infos (1998)
SV: Text in coloums... (2000)
FEW QUESTIONS (1997)
PIXO support (1997)
WebCatalog [FoundItems] Problem - AGAIN - (1997)
Text data with spaces in them... (1997)
Beta Bug in prefs (1997)