jmblog / color-themes-for-google-code-prettify Goto Github PK

Hello! Thank you for this beauty. Are you planning to add a bower support. It will be easier to install it.

The xmp tag allows you to use html without escaping the characters, and the tomorrow night theme doesn't have styles for that HTML tag.

This needs to be added to the stylesheet:

xmp.prettyprint { // styles here }

Hello, I'm just trying to use any of the themes provided by you but, when I put the stylesheet it looks like this (any theme wraps lines):

tomorrow.css

tomorrow-night.css

When using the default prettify.css code looks good:

What could be the issue?

Thanks!

I am looking here:
https://github.com/google/code-prettify

and here:
https://rawgit.com/google/code-prettify/master/examples/quine.html

I see this example:

<script src="https://rawgit.com/google/code-prettify/master/loader/run_prettify.js?autoload=true&amp;skin=sunburst&amp;lang=css" defer=""></script>

note it has skin=sunburst as a query option param in the url..

so how do we load these themes in this repo?
can we use the skin option as a query parameter or..?

Your themes are beautiful, but I notice you use the menlo font. Menlo is a Mac OS X-only font. Menlo is based on Bitstream Vera Sans Mono, and DejaVu Sans Mono is another public-domain derivative of Bitstream; both also have decent install bases. Therefore I propose that after menlo is declared, "DejaVu Sans Mono" and "Bitstream Vera Sans Mono" are the first two fallbacks. This will provide a more visually equal font rendering on non-Mac OS X platforms.

I know it's simple to add it to the CSS ourselves after downloading the file, but I was at first disappointed that the rendered text didn't look like it does in the images. It wasn't until I looked into it that I found out it's because the font depicted is Mac OS X only and added equivalent cross-platform fonts (the two mentioned). Not everyone who comes across this font will look that far into it, so having it added by default will provide a more uniform experience.

Great idea and execution. It would be convenient to add dynamic form for testing own snippets on the site.

Browsers tested:
Chrome 63.0.3234.0
Firefox 56.0
Safari 10.1.2

Chrome:

Firefox:

Safari:

Highlighted code:

<pre class="prettyprint lang-sh"><code>
$ git stash apply
On branch features-from-fbone
Your branch is up-to-date with 'origin/features-from-fbone'.

Changes not staged for commit:
&nbsp; (use "git add &lt;file&gt;..." to update what will be committed)
&nbsp; (use "git checkout -- &lt;file&gt;..." to discard changes in working directory)

<span style="white-space: pre;"> </span>modified:&nbsp; &nbsp;model.py
<span style="white-space: pre;"> </span>modified:&nbsp; &nbsp;requirements.txt

</code></pre>

Prettyprint class still showing default theme. I added into head:

<link rel="stylesheet" href="https://cdn.rawgit.com/jmblog/color-themes-for-google-code-prettify/master/dist/themes/tomorrow.min.css">

Have little clue?

Thanks

See http://jsfiddle.net/4wMLq/ the upper uses the "linenums" css class. Ugly. Also, I'd like to have line numbers on every line, not just every fifth (silly).

(nice themes, thanks!)

I ported Vim desert theme by @fugalh to google-prettify, but couldn't figure out where to paste it for pull request. Here is the snippet that I use.

.prettyprint {
  background-color: #333; color: #ddd;
  border: 1px solid #888;
  font-size: 90%;
  padding: 5px; 
}
.str { color: #ffa0a0; } /* string  - pink */
.kwd { color: #f0e68c; font-weight: bold; }
.com { color: #87ceeb; } /* comment - skyblue */
.typ { color: #98fb98; } /* type    - lightgreen */
.lit { color: #cd5c5c; } /* literal - darkred */
.pun { color: #fff; }    /* punctuation */
.pln { color: #fff; }    /* plaintext */
.tag { color: #f0e68c; font-weight: bold; } /* html/xml tag    - lightyellow*/
.atn { color: #bdb76b; font-weight: bold; } /* attribute name  - khaki*/
.atv { color: #ffa0a0; } /* attribute value - pink */
.dec { color: #98fb98; } /* decimal         - lightgreen */