From: Rainer M Krug <Rainer@krugs.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: README for bitbucket - export to which format?
Date: Fri, 04 Dec 2015 14:51:30 +0100 [thread overview]
Message-ID: <m2y4dae2zh.fsf@krugs.de> (raw)
In-Reply-To: <874mfyqqv1.fsf@gmx.us> (rasmus@gmx.us's message of "Fri, 04 Dec 2015 14:34:58 +0100")
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Rasmus <rasmus@gmx.us> writes:
> Rainer M Krug <Rainer@krugs.de> writes:
>
>> There are many formats available for READMEs on bitbucket, but
>> unfortunately not org mode (I am staying on bitbucket for private repos
>> and move them to github as soon as they can be made public - matter of
>> finances).
>
> You could try Gitlab. It supports Org.
Interesting - looks like a alternative. Are there any other advantages
over BitBucket?
>
>> So what is the best export format from org for bitbucket READMEs? At the
>> moment I am using text (UTF8) Which works, but I would like to have
>> syntax highlighting and clickable links?
>
> Probably Rst or markdown...
I am using markdown - works, although I have to disable the toc.
Thanks,
Rainer
>
> Rasmus
--
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
PGP: 0x0F52F982
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]
next prev parent reply other threads:[~2015-12-04 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 12:38 README for bitbucket - export to which format? Rainer M Krug
2015-12-04 13:17 ` Jeroen Tiebout
2015-12-04 13:52 ` Rainer M Krug
2015-12-04 13:34 ` Rasmus
2015-12-04 13:51 ` Rainer M Krug [this message]
2015-12-04 14:35 ` Rasmus
2015-12-17 17:59 ` Grant Rettke
2015-12-17 19: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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y4dae2zh.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.