All the compass tests pass and stylesheets compile running the latest
versions of compass and sass. I think you must have an issue that's causing
the wrong version of haml to get loaded when in a rails environment.
Chris



On Fri, Nov 14, 2008 at 12:19 AM, yitzhakbg <[EMAIL PROTECTED]> wrote:

>
> Yes. I'm running the latest version of Haml/Sass.I placed the app in
> the files section of this group in a file name compsamp.tar.gz. It's a
> small Rails app. Pointing the browser to localhost:3000/posts causes
> the problem occurs under the circumstances I mentioned. The stylesheet
> is in the Compass gem in:
> frameworks/blueprint/stylesheets/blueprint/modules/_grid.sass (also
> included in the file section)
>
> On 13 נובמבר, 20:32, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote:
> > I can't check your exact code without the full stylesheet, but the
> > following example works for me:
> >
> >   =column(!n, !last = false)
> >     :float left
> >     @if !last
> >       margin-right = 1
> >     @else
> >       margin-right = 2
> >
> >   foo
> >     +column(2)
> >
> > Are you sure you've got the latest revision? Support for @else was added
> > in r7530593.
> >
> > yitzhakbg wrote:
> > > This sounds similar. I have a problem with @else using the latest haml
> > > from github.
> >
> > > This bombs:
> >
> > > =column(!n, !last = false)
> > >   :float left
> > >   +span(!n)
> > >   @if !last
> > >     +last
> > >   @else
> > >     :margin-right = !layout_grid_margin
> >
> > > While this works OK:
> >
> > > =column(!n, !last = false)
> > >   :float left
> > >   +span(!n)
> > >   :margin-right = !layout_grid_margin
> > >   @if !last
> > >     +last
> >
> > > Same in both:
> > > =last
> > >   :margin
> > >     :right 0
> >
> > > On Nov 6, 10:40 pm, j0llyr0g3r <[EMAIL PROTECTED]>
> > > wrote:
> >
> > >> Chris,
> >
> > >> i found the solution:
> >
> > >> As already said, this doesn't work:
> >
> > >> - elsif([EMAIL PROTECTED])
> >
> > >> but this does:
> >
> > >> - elsif ([EMAIL PROTECTED])
> >
> > >> Mind the whitespace between "elsif" and the brackets....
> >
> > >> Ok, so the haml-parser seems to be pretty upset about where one puts a
> > >> whitespace......
> >
> > >> Thanks for the help!
> >
> > >> On Nov 6, 9:26 pm, "Chris Eppstein" <[EMAIL PROTECTED]> wrote:
> >
> > >>> Please reproduce the problem using a simpler code example that
> doesn't
> > >>> require having your controller... Ideally something that we can pipe
> thru
> > >>> the haml command line and as a gist (http://gist.github.com). Once
> you've
> > >>> done that, I'll happily help you debug the issue.
> > >>> Chris
> >
> > >>> On Thu, Nov 6, 2008 at 12:18 PM, j0llyr0g3r <
> >
> > >>> [EMAIL PROTECTED]> wrote:
> >
> > >>>> Hi Chris,
> >
> > >>>>> elsif works fine in haml just the way you are using it. I think it
> boils
> > >>>>> down to some syntax error in your code. usually a forgotten paren
> or
> >
> > >>>> curly
> >
> > >>>>> brace.
> >
> > >>>> i double-checked my code and i don't see any errors. Furthermore, if
> i
> > >>>> change the "elsif" to "if" the code works, so i assume i use the
> > >>>> "elsif" the wrong way?
> >
> > >>>>> However, can I suggest that you simply dry up this code? You're
> doing the
> > >>>>> same thing three times. Why not set an instance variable to the
> tracks
> >
> > >>>> you
> >
> > >>>>> want to list here and then call your partial once:
> >
> > >>>>> #list_tracks
> > >>>>>   = render :partial => "shared/list_track", :collection =>
> @list_tracks
> >
> > >>>> Thanks for the suggestion, i will do as you proposed.
> >
> > >>>> But i still would like to know why the code above is not working for
> > >>>> future cases when i might need this.........
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
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