This issue is caused by Haml automatically indenting the code it 
outputs. There's an easy way to fix it, though: if you use "~" instead 
of "=" all newlines within <textarea> and <pre> tags are replaced by 
HTML newline escape characters, thus escaping Haml's auto-indentation.

- Nathan

Dave wrote:
> Hi all,
>
> I love the HAML/SASS syntax, awesome. However, I stumbled onto a
> problem that I could only correct by reverting back to RHTML. To
> narrow it down to HAML I created a basic rails app and scaffold,
> renamed edit.rhtml to edit.rhtml_ (trailing underscore), and created a
> new edit.haml file that looks like this:
>
> - form_tag :action => 'update', :id => @page do
>   = render :partial => 'form'
>   = submit_tag 'Edit'
>
> I left the form partial as _form.rhtml.
>
> When the form is rendered the following text: ("aa" followed by a
> blank line followed by "bb", all flush left)
>
> aa
>
> bb
>
> is rendered as:  (this is inside of a textarea tag)
>
> aa
>
>       bb
>
> (six leading spaces before bb)
>
> Also, any further lines will be indented six spaces, including blank
> lines (six blanks). The exact number varied a bit depending on whether
> or not I was using a partial (edit.haml + _form.haml) or just putting
> it all into the one file edit.haml. If I was using partials it would
> indent 8, 10, or even 12 spaces depending on how I was laying out the
> page (this was before I narrowed it down to HAML so I wasn't
> consistent).
>
> If I revert back to RHTML, the leading spaces go away. Any idea why
> this happened?
>
> I am running Rails 1.2.3 on Ruby 1.8.4 on Windows XP.
>
> Thanks in advance,
> -dave
>
>
> >
>
>   


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/haml?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to