Is there a way to tell HAML to leave a tag open?
For example I have 2 partial files, a header and a footer. If I use
HAML on the header it will automatically close and in
the header file.
--
You received this message because you are subscribed to the Google Groups
"Haml" group.
To post to this
\
Amy
On Thu, Jan 21, 2010 at 1:04 PM, Michael Narciso
mailto:narke...@gmail.com>> wrote:
Is there a way to tell HAML to leave a tag open?
For example I have 2 partial files, a header and a footer.
If I use
HAML
... blah blah ...
\
\
Amy
On Thu, Jan 21, 2010 at 1:04 PM, Michael Narciso
mailto:narke...@gmail.com>>
wrote:
Take a look at this script:
http://github.com/narkeeso/haml-sass-file-watcher
I've branched from the original author and added some very basic features.
This will look for changes and saves in files with the extension .haml
and .sass then convert them to .html and .css
The nice thing about u
Hello all,
Just had a brief conversation with Chris Eppstein as he demonstrated
how I can loop through to get my desired result. It went something
like this:
Desired Result:
Code:
- (1..3).each do |i|
%div{:class => "item-#{i}"}
However, I was thinking... why doesn't the following code w
Ah... that's too bad :(
Thanks Alex.
Alex Wallace wrote:
AFAIK, Ruby interpolation is allowed in the attributes but not in the
tag names, which include the shorthand #id and .class for %div's.
Best,
Alex
On Thu, Mar 4, 2010 at 5:44 PM, Michael Narciso <mailto:narke...@gmai
n is allowed in the attributes but not in
the tag names, which include the shorthand #id and .class for %div's.
Best,
Alex
On Thu, Mar 4, 2010 at 5:44 PM, Michael Narciso
mailto:narke...@gmail.com>> wrote:
Hello all,
Just had a brief conversa
Scratch that! It can! Brilliant!
On Mar 4, 6:14 pm, Michael Narciso wrote:
> I'd imagine Ruby code can't be evaluated under a filter such as :textile
> too?
>
>
>
> Chris Eppstein wrote:
> > Yes, that is the state of the current implementation.
>
> > O
I'd prefer no prefix but would be content with $.
Norman Clarke wrote:
I strongly agree that $ will be better than !. As far as deprecations
go, perhaps you could go with first a warning for one release cycle,
and then leave it as a non-default configuration option for another
release cycle
Just wanted to let you know that it's been discovered that:
position:relative - is ignored
position: relative - is not ignored
A friend wrestled with this for about an hour. Either this is an error
or by design. If it's by design then I think an error should be thrown
rather than failing silently
10 matches
Mail list logo
