From mboxrd@z Thu Jan 1 00:00:00 1970 From: Waldemar Quevedo Subject: Re: Title of org files in github not recognized Date: Fri, 2 May 2014 14:44:53 +0900 Message-ID: References: <86iopplmko.fsf@somewhere.org> <53624390.4030300@gmail.com> <86a9b1le22.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b5d524e13306c04f86449aa Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33235) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wg6He-0002i7-0B for emacs-orgmode@gnu.org; Fri, 02 May 2014 01:45:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Wg6Ha-0004F8-Ls for emacs-orgmode@gnu.org; Fri, 02 May 2014 01:45:17 -0400 Received: from mail-ob0-x22d.google.com ([2607:f8b0:4003:c01::22d]:43700) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Wg6Ha-0004Et-Ef for emacs-orgmode@gnu.org; Fri, 02 May 2014 01:45:14 -0400 Received: by mail-ob0-f173.google.com with SMTP id wm4so1412468obc.32 for ; Thu, 01 May 2014 22:45:13 -0700 (PDT) In-Reply-To: <86a9b1le22.fsf@somewhere.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: emacs-orgmode --047d7b5d524e13306c04f86449aa Content-Type: text/plain; charset=UTF-8 Hi, yes this issue would be fixed once Github upgrades the Ruby implementation of the parser. To upgrade the version it takes making a pull request to the github/markup repository so that they bump the version and do the release, but it takes some time before the upgrade is validated (security checks, etc...) There another couple of issues that I would like it that they make it to Github, so once having those tackled I'll see if I can ask one of the maintainers to help out planning for an update soon. Cheers On Fri, May 2, 2014 at 12:21 AM, Sebastien Vauban wrote: > Julian Gehring wrote: > > On 01.05.2014 14:17, Sebastien Vauban wrote: > >> Julian Gehring wrote: > >>> How I can convince github to recognize the '#+TITLE:' field of an > >>> org-file? This should be a 'h1' heading, while it is currently > >>> treated as normal text (for example, see > >>> https://github.com/julian-gehring/vignettes/blob/master/README.org). > >>> I know that this is a problem of the parsing on github's site, but > >>> is anyone aware of a good solution? > >> > >> That was supposed to be solved. > >> > >> See https://github.com/wallyqs/org-ruby/issues/3 > > > > Nice. So it seems that github is using an older version of org-ruby. Is > it > > clear what the update policy/cycle of github for softwares like org-ruby > is? > > Unfortunately, not to me... ;-) > > Best regards, > Seb > > -- > Sebastien Vauban > > > --047d7b5d524e13306c04f86449aa Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi, yes this issue would be fixed once Github upgrades the= Ruby implementation of the parser.

To upgrade the version it = takes making a pull request to the github/markup repository so that they bu= mp the version and do the release, but it takes some time before the upgrad= e is validated (security checks, etc...)
There another couple of issues that I would like it that they make it = to Github, so once having those tackled I'll see if I can ask one of th= e maintainers to help out planning for an update soon.

Cheers


On Fri, May 2, 2014 at 12:21 AM, Sebastien Vauban <= sva-news@mygooglest.com> wrote:
Julian Gehring wrote:
> On 01.05.2014 14:17, Sebastien Vauban wrote:
>> Julian Gehring wrote:
>>> How I can convince github to recognize the '#+TITLE:' = field of an
>>> org-file? =C2=A0This should be a 'h1' heading, while i= t is currently
>>> treated as normal text (for example, see
>>> https://github.com/julian-gehring/vignet= tes/blob/master/README.org).
>>> I know that this is a problem of the parsing on github's s= ite, but
>>> is anyone aware of a good solution?
>>
>> That was supposed to be solved.
>>
>> See https://github.com/wallyqs/org-ruby/issues/3
>
> Nice. So it seems that github is using an older = version of org-ruby. =C2=A0Is it
> clear what the update policy/cycle of github for softwares like org-ru= by is?

Unfortunately, not to me... ;-)

Best regards,
=C2=A0 Seb

--
Sebastien Vauban



--047d7b5d524e13306c04f86449aa--