Hi Waldemar,
Thanks, I'm looking forward to see all these improvements also in github.
Best wishes
Julian
On 02.05.2014 07:44, Waldemar Quevedo wrote:
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
Hi,
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
Julian Gehring julian.gehr...@gmail.com writes:
Hi,
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
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
Hi Seb,
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?
Best wishes
Julian
On 01.05.2014 14:17, Sebastien Vauban wrote:
Julian Gehring wrote:
How I can convince github to recognize
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
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
