From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Rainer M Krug <r.m.krug@gmail.com>
Subject: Re: README.org on github
Date: Mon, 21 May 2012 14:43:24 +0200 [thread overview]
Message-ID: <CAMXnza1snOtSPf3NsKHfdOpDebtQVQ+y4wTi1V5TTV03jL+3cw@mail.gmail.com> (raw)
In-Reply-To: <CALnw1fTi7yhRM3Cdb_bfxkoQ3D3tVi9io2tsu3kLj9GAduORVQ@mail.gmail.com>
Hi Puneeth,
On Mon, May 21, 2012 at 10:57 AM, Puneeth Chaganti <punchagan@gmail.com> wrote:
> Actually, embedding code blocks in the README does work[1][2]. You
> need to use all upper case keywords, i.e., BEGIN_SRC or BEGIN_EXAMPLE
> instead of begin_src or begin_example.
>
> [1] - https://github.com/punchagan/experiri/blob/master/README.org
> [2] - https://raw.github.com/punchagan/experiri/master/README.org
I see source blocks formated as example blocks. Is that the same as you
are seeing? If so, I wouldn't call that support for source blocks. I
would expect to see syntax highlighting like pure source files on
GitHub.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2012-05-21 12:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-18 18:45 README.org on github Rainer M Krug
2012-05-19 7:35 ` Bastien
2012-05-19 9:23 ` Tom Regner
2012-08-03 18:19 ` Bastien
2012-08-04 3:23 ` Waldemar Quevedo
2012-08-04 7:15 ` Bastien
2012-05-21 8:38 ` Rainer M Krug
2012-05-21 8:57 ` Puneeth Chaganti
2012-05-21 9:02 ` Rainer M Krug
2012-05-21 9:57 ` Puneeth Chaganti
2012-05-21 10:05 ` Rainer M Krug
2012-05-21 12:43 ` suvayu ali [this message]
2012-05-21 13:29 ` Tom Regner
2012-05-22 15:54 ` suvayu ali
2012-05-22 16:02 ` Puneeth Chaganti
2012-05-22 23:19 ` Bastien
2012-05-22 23:16 ` Bastien
2012-05-20 4:03 ` François Pinard
2012-05-20 22:05 ` Neil Smithline
2012-05-21 8:43 ` Rainer M Krug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMXnza1snOtSPf3NsKHfdOpDebtQVQ+y4wTi1V5TTV03jL+3cw@mail.gmail.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=punchagan@gmail.com \
--cc=r.m.krug@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).