From: Rainer M Krug <r.m.krug@gmail.com>
To: Puneeth Chaganti <punchagan@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: README.org on github
Date: Mon, 21 May 2012 12:05:01 +0200 [thread overview]
Message-ID: <4FBA134D.4020506@gmail.com> (raw)
In-Reply-To: <CALnw1fSw3TjoN5pj6jpRoVViDgdMK=QVbpjQH5wR=J=quWAnoA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 21/05/12 11:57, Puneeth Chaganti wrote:
> On Mon, May 21, 2012 at 2:32 PM, Rainer M Krug <r.m.krug@gmail.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> On 21/05/12 10:57, Puneeth Chaganti wrote:
>>> On Mon, May 21, 2012 at 2:08 PM, Rainer M Krug <r.m.krug@gmail.com> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>>>
>>>> On 19/05/12 09:35, Bastien wrote:
>>>>> Hi Rainer,
>>>>>
>>>>> Rainer M Krug <r.m.krug@gmail.com> writes:
>>>>>
>>>>>> I would like to use a README.org file on github, and also include code blocks in the
>>>>>> README.org - is this possible?
>>>>>
>>>>> No.
>>>>
>>>> To bad ...
>>>
>>> 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.
>>
>> Great - then I will change this in my .org file.
>>
>> Now I just began to prefer the small-letter version...
>
> Yes, I too prefer the lower-case version, and this has been fixed in the latest version of
> org-ruby. But, the version that GitHub uses is a very old one, and somebody opened an issue
> [1] to update the version being used.
Good to know, that I am not the only one...
Cheers,
Rainer
>
> [1] - https://github.com/github/markup/issues/117
- --
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys.
(Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk+6E00ACgkQoYgNqgF2egqA5ACeL7UF9XbdWpqeECILjcQ9Npjg
GDkAn18xqJvCxGXIUjvoC3MZd4xSVGl6
=DiPC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-05-21 10:05 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 [this message]
2012-05-21 12:43 ` suvayu ali
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=4FBA134D.4020506@gmail.com \
--to=r.m.krug@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=punchagan@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).