@macdrifter, thank you very much. It was awesome to find out you helped implement the critical markup.
Ok, quick CSS question to the experts here. Is there a way to apply the CSS format to everything underneath the tag?
For example. Sometimes I have a series of tasks that are done almost simultaneously, so it is easier to tag the project as @done instead of tagging all the individual tasks. I want all the children to also have the @done attributes.
I am also wondering if it is possible to change the color of a tag based on the value of it. Something like
In TaskPaper all is divided into runs. All text is part of one and only one run. Each run has a set of attributes. The end goal when styling runs is to map from TaskPaper model runs to rich text runs… so map from TaskPaper things like, tag, lead, and display to rich text things like font, color, background.
The actual syntax says:
run[display]{ apply these attributes }: For any run that includes the “display” attribute “apply these attributes”.
With that in mind “display” is an attribute in TaskPaper attribute runs that is applied to all “non syntax” text content. In particular the display attribute is applied everywhere except:
Not applied to leading dash in tasks
Not applied to trailing colon on projects
Not applied to trailing list of tags
The primary use (why I added it) of the display attribute is so that when items are tagged done I can make the strikethrough go just through the task “text” and not through the trailing @done tag and the leading dash. The other use for it is that when I generate the project names in the project sidebar notice that the trailing colon and tags are not included… this is because I only include text in the sidebar that has the “display” attribute.
PS
“display” is probably a bad name for this attribute, in the future I might change it to “content”, that’s maybe a more descriptive name for what this attribute does… mark “content” text separate from “syntax” text.
// colors the entire tag rule (@, name, value and ()'s)
run[tag=data-priority] {
color: green;
}
// colors just the tag @ and name runs
run[tagname=data-priority] {
color: blue;
}
// colors just the tag value run.
run[tagvalue=high] {
color: orange;
}
But note that run[tagvalue=high] would also match the “high” text in @someothertag(high). If you want to be more specific, and color the tag name based on the tag value you could use rules like this:
I’ve just been trying, and failing, to use font-variant: small-caps; in a theme for the project names. Just wanted to check: Is this part of .less not supported?
If you want small caps I think you could just refere directly to the small caps variants font file name (probably have all those terms messed up), but I think it should be possible by using right value for @font-family.