Re: [WebDNA] can webdna's [grep] find and replace ONLY the literal
This WebDNA talk-list message is from 2012
It keeps the original formatting.
numero = 109019
interpreted = N
texte = Govinda wrote: [snip] I mean, an [url] wrapper like this makes sense in the context of my/our understanding described in this paragraph: > > [grep search=[url][+][/url]&replace=something] > > ...but does not work. [snip] Yes, that is how it should probably work in the future. For now, it is good to know that the ASCII equiv. seems to work in many cases. Note, I think you are right that it is high-time we start documenting WebDNA's grep. Grep in WebDNA is an old open-source "egrep" parser that has evolved over the years via several developers, ending with a couple changes from SMSI (which *was* documented.. ie. IgnoreCase). So, that is the main reason why there is not good documentation on it right now. I think this is a case where all of us developers will need to start writing down our findings on WebDNA's grep to start the documentation unfortunately. It's not the preferred way, but in this case, It's just going to have to be that way. One way we can do this is via interactive documentation. I know the "new" docs are not interactive, but since I have a new position with WSC, I will work on making that happen down the road a bit. Cheers, Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]**
Associated Messages, from the most recent to the oldest:
Govinda wrote: [snip] I mean, an
[url] wrapper like this makes sense in the context of my/our understanding described in this paragraph: > > [grep search=
[url][+][/url]&replace=something] > > ...but does not work. [snip] Yes, that is how it should probably work in the future. For now, it is good to know that the ASCII equiv. seems to work in many cases. Note, I think you are right that it is high-time we start documenting WebDNA's grep. Grep in WebDNA is an old open-source "egrep" parser that has evolved over the years via several developers, ending with a couple changes from SMSI (which *was* documented.. ie. IgnoreCase). So, that is the main reason why there is not good documentation on it right now. I think this is a case where all of us developers will need to start writing down our findings on WebDNA's grep to start the documentation unfortunately. It's not the preferred way, but in this case, It's just going to have to be that way. One way we can do this is via interactive documentation. I know the "new" docs are not interactive, but since I have a new position with WSC, I will work on making that happen down the road a bit. Cheers, Donovan -- Donovan Brooke WebDNA Software Corporation http://www.webdna.us **[Square Bracket Utopia]**
Donovan Brooke
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:
Huge databases and RAM (1998)
RE: Credit card processing - UK (1997)
Car Database (2002)
add line item context and showitems (1998)
Multi Actions (1999)
Here we go again... (2006)
Running 2 two WebCatalog.acgi's (1996)
Hiding Email Addresses (2003)
2.0Beta Command Ref (can't find this instruction) (1997)
error: Too many nested [xxx] contexts (1997)
Error:Too many nested [xxx] contexts (1997)
emailer w/F2 (1997)
[WebDNA] Anyone used these people ? (2010)
Summing fields (1997)
problems with 2 tags shakur (1997)
docs for WebCatalog2 (1997)
Protect tag for large groups? (1999)
Accented chars and emailer (1998)
Verifying both name and password (was: THANKS) (1997)
PCS Frames-Default page is solution! (1997)