I use Jekyll and Markdown on Github for my blog. How to embed code tags on my page?

Question

I use Jekyll and Markdown for Github for my blog. How to embed code tags on my page?

For example, I thought I could use <pre> tags to insert some code bindings into my page for display to readers, but they don’t like jekyll.

Can someone please tell me a nice formatting tag that I can use for this to insert code into my page.

if I try this code:

 <pre> <code class="ruby"> git clone --mirror [e-mail] :project project cd project git remote add github [e-mail] :username/project.git In cron Job cd /pathto/project && git fetch -q && git push -q --mirror github </code> </pre> 

I get this error

My _config.xml

 # This is the default format. # For more see: https://github.com/mojombo/jekyll/wiki/Permalinks permalink: /:categories/:year/:month/:day/:title exclude: [".rvmrc", ".rbenv-version", "README.md", "Rakefile", "changelog.md"] auto: true pygments: true # Themes are encouraged to use these universal variables # so be sure to set them if your theme uses them. # title : xxxx tagline :xxxx author : name : xxx email : jxxx github : xxx twitter : xx # The production_url is only used when full-domain names are needed # such as sitemap.txt # Most places will/should use BASE_PATH to make the urls # # If you have set a CNAME (pages.github.com) set your custom domain here. # Else if you are pushing to username.github.com, replace with your username. # Finally if you are pushing to a GitHub project page, include the project name at the end. # production_url : http://johnathanmarksmith.com # All Jekyll-Bootstrap specific configurations are namespaced into this hash # JB : version : 0.3.0 # All links will be namespaced by BASE_PATH if defined. # Links in your website should always be prefixed with {{BASE_PATH}} # however this value will be dynamically changed depending on your deployment situation. # # CNAME (http://yourcustomdomain.com) # DO NOT SET BASE_PATH # (urls will be prefixed with "/" and work relatively) # # GitHub Pages (http://username.github.com) # DO NOT SET BASE_PATH # (urls will be prefixed with "/" and work relatively) # # GitHub Project Pages (http://username.github.com/project-name) # # A GitHub Project site exists in the `gh-pages` branch of one of your repositories. # REQUIRED! Set BASE_PATH to: http://username.github.com/project-name # # CAUTION: # - When in Localhost, your site will run from root "/" regardless of BASE_PATH # - Only the following values are falsy: ["", null, false] # - When setting BASE_PATH it must be a valid url. # This means always setting the protocol (http|https) or prefixing with "/" BASE_PATH : false # By default, the asset_path is automatically defined relative to BASE_PATH plus the enabled theme. # ex: [BASE_PATH]/assets/themes/[THEME-NAME] # # Override this by defining an absolute path to assets here. # ex: # http://s3.amazonaws.com/yoursite/themes/watermelon # /assets # ASSET_PATH : false # These paths are to the main pages Jekyll-Bootstrap ships with. # Some JB helpers refer to these paths; change them here if needed. # archive_path: /archive.html categories_path : /categories.html tags_path : /tags.html atom_path : /atom.xml rss_path : /rss.xml # Settings for comments helper # Set 'provider' to the comment provider you want to use. # Set 'provider' to false to turn commenting off globally. # comments : provider : disqus disqus : short_name : jekyllbootstrap livefyre : site_id : 123 intensedebate : account : 123abc facebook : appid : 123 num_posts: 5 width: 580 colorscheme: light # Settings for analytics helper # Set 'provider' to the analytics provider you want to use. # Set 'provider' to false to turn analytics off globally. # analytics : provider : google google : tracking_id : 'UA-123-12' getclicky : site_id : mixpanel : token : '_MIXPANEL_TOKEN_' # Settings for sharing helper. # Sharing is for things like tweet, plusone, like, reddit buttons etc. # Set 'provider' to the sharing provider you want to use. # Set 'provider' to false to turn sharing off globally. # sharing : provider : false # Settings for all other include helpers can be defined by creating # a hash with key named for the given helper. ex: # # pages_list : # provider : "custom" # # Setting any helper provider to 'custom' will bypass the helper code # and include your custom code. Your custom file must be defined at: # ./_includes/custom/[HELPER] # where [HELPER] is the name of the helper you are overriding. 

Answer 1

If the "page" you are linking to is a Markdown file, that is, the extension is .md or .markdown, then you will want to use the standard Markdown syntax:

For inline code use backlinks, for example: `inline code`

For block code specify each line with 4 spaces:

 block of code 

Jekyll uses a Markdown analyzer such as RedCarpet, Maruku or RDiscount, and does not determine how you should format your content, which is determined by the type of content you write, in this case Markdown. So, the place to look is Markdown's syntax documentation for code :

http://daringfireball.net/projects/markdown/syntax#code

You can also see syntax highlighting using the {% highlight %} Liquid syntax tag:

https://github.com/mojombo/jekyll/wiki/Liquid-Extensions#code-highlighting

Hope this helps!

Answer 2

How about this sir

 ~~~ ruby # This is a test. def foo puts 'foo' end ~~~ 

ref