emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: Tom Regner <tom@goochesa.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: README.org on github
Date: Tue, 22 May 2012 17:54:39 +0200	[thread overview]
Message-ID: <CAMXnza0PRNWBqprSqzgzGfDijw1NBaDofy9p0jAixiq7ZeC4oQ@mail.gmail.com> (raw)
In-Reply-To: <87obphwtlp.fsf@goochesa.de>

Hi Tom,

On Mon, May 21, 2012 at 3:29 PM, Tom Regner <tom@goochesa.de> wrote:
> Hi,
>
> suvayu ali <fatkasuvayu+linux@gmail.com> writes:
>
>> 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.
>
> org-ruby is in it's current form not capable to do that, but it's
> currently actively developed [fn:1] (maybe not for org-mode standards :-D, the last
> commit was 8 days ago) and there are a few items on the todo list.
>
> And all shortcomings aside, an update on github/markups side would at
> least make the usage of org-documents on github bearable.
>

Sorry if my comments seemed like a complaint/gripe. When an org-mode
user says, "feature bla" is supported they usually mean the whole
thing, with all the bells and whistles (e.g. source block would imply
with syntax highlighting). So I just wanted to clarify it was
incorrect to say "source blocks are supported".

> Only sufficient demand for org-documents will foster betterment I guess.
>

Yes I realise that. I have never interacted with GitHub staff for
feature requests. Being a long time org-mode user (post-6.33, that's
ages in org years :-p), maybe I should give that a try.

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2012-05-22 15:55 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
2012-05-21 13:29         ` Tom Regner
2012-05-22 15:54           ` suvayu ali [this message]
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=CAMXnza0PRNWBqprSqzgzGfDijw1NBaDofy9p0jAixiq7ZeC4oQ@mail.gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tom@goochesa.de \
    /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).