You're looking at Less Wrong's discussion board. This includes all posts, including those that haven't been promoted to the front page yet. For more information, see About Less Wrong.

gwern comments on Case Study: Reading Edge's financial filings - Less Wrong Discussion

15 Post author: gwern 06 September 2011 03:46AM

You are viewing a comment permalink. View the original post to see all comments and the full post content.

Comments (13)

You are viewing a single comment's thread.

Comment author: gwern 06 September 2011 03:58:47AM 1 point [-]

If anyone knows how to fix the spacing problem, I'd appreciate it. It looks absolutely correct when I go to edit it, which makes sense since I wrote it correctly and Pandoc generated its usual HTMl.

Comment author: Vladimir_Nesov 06 September 2011 07:53:37AM *  4 points [-]

Fixed, and changed formatting on the chat log (was it sensible in your browser? In Chrome, it looked like a single very long line with a horizontal scrollbar).

Somehow the markup doesn't like <div>, which you used to set the anchors. Replacing those with <a name="..."></a> fixed the missing spaces problem.

Comment author: gwern 06 September 2011 12:54:05PM 0 points [-]

was it sensible in your browser? In Chrome, it looked like a single very long line with a horizontal scrollbar

It worked before in Firefox; Pandoc generates the correct code from multiple heavily indent lines, so I think this is just another Chrome rendering bug. (It does that a lot - for example, the MathML on gwern.net apparently breaks in Chrome.)

Comment author: Douglas_Knight 06 September 2011 03:53:56PM 0 points [-]

I saw the single large scroll bar in Firefox 5. In fact, I saved the old markup and it has a <pre><code> with no linebreaks inside. If you didn't see the scroll bar, it's because you didn't look at it on LW.

Comment author: grouchymusicologist 06 September 2011 04:31:54AM 1 point [-]

As a data point, it shows up correctly in the RSS feed.

Comment author: shokwave 06 September 2011 04:40:33AM *  0 points [-]

More spaces? It looks like the html is eating the spaces around it, but not other characters - see where you linked to Amazon S3, for example. Maybe two spaces either side of the html links will result in only one getting eaten. More a bandaid than a fix, but eh.