Right. I read that and tried the filter idea before posting. For whatever
reason, the filter didn't work - it's working now so it was undoubtedly some
screw up on my part.
What really hung me up was the notion that the component starts immediately
after the tag, *not* on the line following the tag. In other words the
following are not equivalent:
<%def .mycomponent>
Hi
</%def>
<%def .mycomponent1>Hi</%def>
My mental block was the erroneous idea that the component didn't start until
the line after the tag. I expected .mycomponent to work the way
.mycomponent1 does. Now I know better.
- Alan
From: Jonathan Swartz [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 05, 2007 9:38 AM
To: Timothy S.Nelson
Cc: Alan Humphrey; 'Sherrard Burton'; mason-users@lists.sourceforge.net
Subject: Re: [Mason] newline before component results
This is a FAQ:
http://www.masonhq.com/?FAQ:Components#h-why_does_my_output_have_extra_newli
nes_whitespace_and_how_can_i_get_rid_of_it_
On Aug 3, 2007, at 5:25 PM, Timothy S. Nelson wrote:
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
