Re: removing programming logic white space

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 50990
interpreted = N
texte = I use the following grep around most of my pages:[grep search=[%0D%0A][%0D%0A%09]*&replace=%0D]lots of page code filled withblank lines and tab-indents here[/grep] This grep executes much faster than a bunch of comments, and leaves the code easier to read. The only thing to watch out for is pages with textarea fields where you may want to preserve returns, line feeds and tabs.- brianOn Monday, June 9, 2003, at 10:32 AM, devaulw@onebox.com wrote:> This topic is covered extensively in the archives. You can either > wrap the entire page in a grep or convertwords context so that the > whitespace is removed or you can wrap each line ending like this: > [/!][search db=search.db][!] > [/!][numfound][!] > > This way the line endings are commented out. This can be done with a > grep search/replace in BBEdit very easily. Be careful not to remove > the line endings where you need them, for example in a writefile > context. > Or you could get used to the whitespace. > > -----Original Message----- > From: Lucas Rockwell > Sent: Mon, 9 Jun 2003 10:22:33 > To: (WebDNA Talk) > Subject: removing programming logic white space > > Hi all, > > Is there a way to remove the programming logic white space from the > output of a template? > > For instance, if I have a template with 20 lines of WebDNA code (all > of it logic), the resulting html output has 20 blank lines in it. This > is a real annoyance, especially when trying to format email messages. > > Is there a way to have WebDNA not output blank lines and just output > what it's supposed to output? > > Thanks. > > -lucas ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Associated Messages, from the most recent to the oldest:

    
  1. Re: removing programming logic white space (Rob Marquardt 2003)
  2. Re: removing programming logic white space (Kenneth Grome 2003)
  3. Re: removing programming logic white space (Dale LaFountain 2003)
  4. Re: removing programming logic white space (Brian Fries 2003)
  5. Re: removing programming logic white space (Alain Russell 2003)
  6. Re: removing programming logic white space (Rob Marquardt 2003)
  7. Re: removing programming logic white space (Alain Russell 2003)
  8. Re: removing programming logic white space (Rob Marquardt 2003)
  9. Re: removing programming logic white space (Dale LaFountain 2003)
  10. Re: removing programming logic white space (Lucas Rockwell 2003)
  11. Re: removing programming logic white space (Rob Marquardt 2003)
  12. Re: removing programming logic white space (Glenn Busbin 2003)
  13. Re: removing programming logic white space (Rob Marquardt 2003)
  14. Re: removing programming logic white space (Brian Fries 2003)
  15. Re: removing programming logic white space (Rob Marquardt 2003)
  16. Re: removing programming logic white space (Lucas Rockwell 2003)
  17. Re: removing programming logic white space (Brian Fries 2003)
  18. Re: removing programming logic white space (Lucas Rockwell 2003)
  19. Re: removing programming logic white space (devaulw@onebox.com 2003)
  20. removing programming logic white space (Lucas Rockwell 2003)
I use the following grep around most of my pages:[grep search=[%0D%0A][%0D%0A%09]*&replace=%0D]lots of page code filled withblank lines and tab-indents here[/grep] This grep executes much faster than a bunch of comments, and leaves the code easier to read. The only thing to watch out for is pages with textarea fields where you may want to preserve returns, line feeds and tabs.- brianOn Monday, June 9, 2003, at 10:32 AM, devaulw@onebox.com wrote:> This topic is covered extensively in the archives. You can either > wrap the entire page in a grep or convertwords context so that the > whitespace is removed or you can wrap each line ending like this: > [/!][search db=search.db][!] > [/!][numfound][!] > > This way the line endings are commented out. This can be done with a > grep search/replace in BBEdit very easily. Be careful not to remove > the line endings where you need them, for example in a writefile > context. > Or you could get used to the whitespace. > > -----Original Message----- > From: Lucas Rockwell > Sent: Mon, 9 Jun 2003 10:22:33 > To: (WebDNA Talk) > Subject: removing programming logic white space > > Hi all, > > Is there a way to remove the programming logic white space from the > output of a template? > > For instance, if I have a template with 20 lines of WebDNA code (all > of it logic), the resulting html output has 20 blank lines in it. This > is a real annoyance, especially when trying to format email messages. > > Is there a way to have WebDNA not output blank lines and just output > what it's supposed to output? > > Thanks. > > -lucas ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ Brian Fries

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:

session handling (2004) Searching for all records (1998) Site Builder & IE Mac (2004) Help formatting search results w/ table (1997) More Shopping Cart Problems (2000) The List is Changing (1997) Setting up shop (1997) WebCat2b14MacPlugIn - [include] doesn't hide the search string (1997) pdf files? (2001) Signal Raised Error (Part III) (1997) WebCat2b15MacPlugIn - [authenticate] not [protect] (1997) What am I missing (1997) vars (2000) suffix mapping, use of cache, etc. (1997) AOL and webcat (1998) b18 problem on NT 4.0 (1997) (1997) Running 2 two WebCatalog.acgi's (1996) results in a table (2000) Error Lob.db records error message not name (1997)