intertwingly

It’s just data

The President’s challenge

I agree with Wendy - they need to find another way. I understand the piracy concerns, but giving up free speech is not the way to go.

Randy

Posted by Randy

The President’s challenge

It’s been very hard to vocalize against SOPA when I live in Nashville and 1/3 of my contacts are in the music business, who all want it passed. I still have to speak out that it is a bad law and that my musician friends need to find another way. I have no idea what the Committee is going to do with it now that it is back in their laps for reconsideration.

Thanks for the link to Lockdown. That was a blast from the past for me.

Wendy

Posted by Wendy

Wunderbar

Giulio: You definitely will get a closing tag if there is any nested content.  The relevant difference is when there is no nested content.  Consider:

_script src="/jquery-min.js"

vs:

_br

In the former, you want a close tag (at least when the content is served with the MIME type of text/html).  In the latter you do not.

In the example cited, if you omit the !, the output will look like this:

<p>
  Hello 
  <span class="name">Sam</span>
  !
</p>

While pretty, this will have the unfortunate side effect of inserting a space between the name and the exclamation mark in the output.

Posted by Sam Ruby

Wunderbar

Both the paragraph created by _p "Hello #{$param.name}!" in the first example and the one created by _p! { _ "Hello "; _span $param.name, class: 'name'; _ '!' } in the exclamation-mark-overrides-closing-tag-behavior example show opening and closing tags for p. Just a typo, a bug, or am I missing something about the exclamation mark overriding feature?

Posted by Giulio Piancastelli

Post number 9749

In a previous thread , crunchland said: knowing people’s sock puppets or making IP’s public would so let the steam out of threads like this . And today I was looking over comments on this post . If one hovers over the commentator’s name one can see...

Excerpt from Comments on: Comments on 9749