From: Bastien <bzg@gnu.org>
To: Waldemar Quevedo <waldemar.quevedo@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: README.org on github
Date: Sat, 04 Aug 2012 09:15:39 +0200 [thread overview]
Message-ID: <874nojb010.fsf@gnu.org> (raw)
In-Reply-To: <CALzn4yi3Js4POitSwqN7DC0VSCtCYVAy-dpVnxvOgDzKuqeL3g@mail.gmail.com> (Waldemar Quevedo's message of "Sat, 4 Aug 2012 12:23:05 +0900")
Waldemar Quevedo <waldemar.quevedo@gmail.com> writes:
> My name is Waldemar, and I am the current maintainer of the org-ruby
> gem.
> It looks like thanks to you (and many others who reported this)
> github/markup was updated so that it uses the 0.7.0 org-ruby version
> of the gem!
> https://github.com/github/markup/commit/
> b0144938d42c4e0b0f308c4e9cb1e5a23c155c72
Wow, that's great news, thanks!
> I know that org-ruby html export implementation is far from perfect,
> but this will improve some things until a better solution that fits
> Github backed is build. For example, syntax highlighting #+begin_src
> blocks through Pygments should be available in Github with this
> release (in theory).
I tried both Elisp and C code in a #+begin_src block, but it didn't get
highlighted on github. Not a big problem, really, but exactly the kind
of thing that will help README.org files take the world over :)
Again, great news,
--
Bastien
next prev parent reply other threads:[~2012-08-04 7:15 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 [this message]
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
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=874nojb010.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=waldemar.quevedo@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).