GitHub gist changes break gist plugin formatting

[lukekarrys]

Not sure exactly what the issue is but GitHub updated their gists today and it looks like it breaks a few things with regards to the gist plugin.

Here is how a gist on my site looks: http://lukecod.es/blog/2012/02/14/pitchfork-dot-com-album-rating-api/

It looks like at least two things are broken:

• That page (source) is only supposed to bring in one gist file and now it brings in all files
• Formatting and styling

I plan to take a look at this over the next couple days, but thought I'd open an issue to avoid duplicates and in case anyone wants to take a look at it sooner.

[parkr]

Just taking a look into it now.

Taking a look at the gist plugin, it looks like everything is working (URL endpoints, etc, are all still functional).

It's probably the case that the new gist styling in the script file (gist.github.com/gist_no.js) is including new CSS (complete with !important's... ugh) which is interfering with the styles. I'll see if I can track down the offending styles.

[parkr]

Shite, Github has eff'd this all up.

@imathis, I'd recommend throwing out the script thing (.js) altogether and just using the code. Github's added waayyy too many styles, most of which has !important's. Yikes!

[parkr]

_syntax.scss will definitely have to be changed, to match the new gist output hierarchy:

[parkr]

Perhaps instead of

html .gist .gist-file .gist-syntax .gist-highlight

in the first line, we have:

html .gist .gist-file .gist-syntax .highlight

to match:

[parkr]

It also looks like a Gist-wide issue (perhaps a fix is on its way?):

(from Github Flavored Markdown page)

Looks like they also broke embeds that don't specify a file name - doesn't display anything at all (and thus broke all of mine)

[mttrb]

I have got my gists so that they are at least displaying now (although horribly formatted) by adding a specific filename. However, one of my gists was pointing at an Objective-C category file with the name NSArray+NegativeIndexes.m. The + sign in this filename was also causing the gist to not display, presumably being interpreted as a space in the URL. I had to change the gist tag in my post to escape the + with a %2B. I assume this escaping should be done within Octopress/Liquid.

[ritalin]

My gist code embedded gist page involves right justify and a deal of new lines.
For your information, Deleting line 24 (line-height: 2), line 25 (text-align: justify) and line 98 - 100 (td{text-align: center;}) in _article.scss lead to display correctly.
But the line number has been broken yet.

PR #849 fixes the issue of Gists not showing because of the missing file name - still looks horrible, but at least the content is there.

[imathis]

I'm on this, I'll have a fix up hopefully tonight. While it's nice to be able to use Gists to embed things, I think this is a good time to point out, having external content isn't generally a good practice.

1. When editing a post, you have to go to manage content in multiple places. This is a pain.
2. The source can change things and break your embed codes, styling overrides, etc.
3. Additional requests slow down rendering and when the source is down, your pages are incomplete.

There are some good use cases for gists, but in general I recommend switching to locally generated code. Remember you can still link out to the gist like this:

``` [lang] [description] [url] [download link text]
some code here
```

This way you can still link to gists to allow people to fork, comment, and user other cool gist features.

[troygoode]

I was able to temporarily resolve this using the fix from #849 and the following CSS overrides:

.highlight {
  background: none !important;
}
.line_numbers {
  line-height: 18px;
  font-size: 13px;
}

[parkr]

We're re-writing the Gist plugin, and this will be dealt with then.

[kitchen]

just to clarify, this is still 'broken', yes? I just updated to master and my gists are still a little 'off'... the background color only extends to the right as far as the longest line even though the bounding box is wider than that.

example:
http://blog.kitchen.io/archive/2012/08/22/my-mutt-setup/

If it's still broken, that's fine, I'm patient, I just want to make sure I haven't broken something on my own accord :)

[parkr]

Yep it's still "broken" on the master branch. The 2.1 branch has a fix if you want that.