emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Pizzolli <dan@toel.it>
To: Thomas Koch <thomas@koch.ro>
Cc: emacs-orgmode@gnu.org
Subject: Re: org the program vs. org the format
Date: Tue, 09 Dec 2014 00:10:31 +0100	[thread overview]
Message-ID: <8661dlybyw.fsf@me.localhost.invalid> (raw)
In-Reply-To: <1595178.LtFOMbouyD@x121e> (Thomas Koch's message of "Mon, 08 Dec 2014 23:00:20 +0100")


Hello Thomas,

Thomas Koch writes:

> Hi,
>
> there's a discussion on emacs-devel[1] about replacing texinfo as the 
> documentation format and org is mentioned. RMS correctly mentions that org-
> mode is not a format but a program.
>
> This was also my problem when I thought about using org-mode at work in my 
> team. Since I'm the only emacs user we decided to use asciidoc which is a 
> format that can be edited and processed with different programs.
>
> So org-mode is a bit like PHP which also doesn't (didn't) have a specification 
> but the implementation is the specification.
>
> Would it be possible to change the format of org-mode to be a superset of e.g. 
> asciidoc or markdown but keep the features?

Sorry for not answering directly but I am not enough knowledgeable.

I like to point out that there is an ongoing attempt to specify the org
syntax[1], and that there are translators[2] and tools[3] that can work
with org source files.

My personal workaround (but I am not sure it can scale for a community)
is to have emacs and all the org dependencies packaged in a lightweight
virtual machine.  A set of script take care to send the org files to the
vm and retrieve the results.  Unfortunately my approach is quite rough,
and I am not aware of any recent attempt to offer org-mode as a
service[4].  If you have some degree of control of your build/continuous
integration server I guess this is a viable solution.

My use case is to have a clean environment where build a reproducible doc
using babel, IMHO not so farm from using org for creating documentation.

Like you I also have problem in sharing the result and the work, because
of the high step for newcomers that do know little about emacs, command
line and scripting.  I think that we have some good examples for solving
this, see for example the ipython notebook[5] and rmarkdown[6], both
projects month after month gain more and more adoption.  The great power
of org is still winning for me, but I keep an eye on other approaches.

Best,
Daniele

[1] http://lists.gnu.org/archive/html/emacs-orgmode/2014-09/msg00599.html
[2] http://orgmode.org/worg/org-translators.html
[3] http://orgmode.org/worg/org-tools/index.html
[4] http://lists.gnu.org/archive/html/emacs-orgmode/2012-03/msg01097.html
[5] http://ipython.org/notebook.html
[6] http://rmarkdown.rstudio.com/

  reply	other threads:[~2014-12-08 23:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 22:00 org the program vs. org the format Thomas Koch
2014-12-08 23:10 ` Daniele Pizzolli [this message]
2014-12-08 23:54 ` Rasmus

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=8661dlybyw.fsf@me.localhost.invalid \
    --to=dan@toel.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=thomas@koch.ro \
    /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).