From: Bastien <bzg@gnu.org>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
"Thomas S. Dye" <tsd@tsdye.com>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Proposal for new/updated exporter tutorials on Worg
Date: Mon, 08 Apr 2013 17:30:56 +0200 [thread overview]
Message-ID: <87r4ik29xs.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+M2ft-v_GEr3wXLuo+uieELXz7NRpz98mHSL9cpsS8vBaNKDg@mail.gmail.com> (John Hendy's message of "Sun, 31 Mar 2013 23:58:44 -0500")
Hi John,
John Hendy <jw.hendy@gmail.com> writes:
>> What do you think?
>
> Not sure how to implement this, but sounds reasonable.
Thanks. So basically the idea is just to use
#+PROPERTY: OrgCompat 8.0
on top of Worg files that contain 8.0-only information, and
:PROPERTIES:
:OrgCompat: 8.0
:END:
in sections that are 8.0-only.
I started to do this with the new tutorial I just pushed about agenda
filtering/limiting:
http://orgmode.org/worg/org-tutorials/agenda-filters.org
We don't need to update Worg systematically at this point, just keep
this property in mind when we write new stuff.
> I'd like to get
> everything export related into it's own directories, if possible.
Sounds reasonable.
> ox-template.org is now pushed as well. It's modified from
>ob-doc-template.org.
Thanks for all these updates!
> [1] As an aside, is there a good reference for what Worg should/could
> contain and what should live in the manual? I've noticed recently on
> the list that, for example, :wrap was documented in the manual even
> though =:results output wrap= came up on the mailing list and was not
> in the Worg summary of header options. If too much is duplicated, it
> make for double the things to track...
The manual is a trade-off between completeness and minimalism: it
reflects current fonctionalities and tries to give the minimal info
needed for the max number of features.
Worg is a trade-off between inclusiveness and precision: because it is
inclusive (contributors are welcome to write 10-pages tutorial about
an obscure feature), and because it's too hard to delete obsolete
information, it lacks accurateness sometimes -- hence the OrgCompat
trick, which will make things better.
As for where to add things first, contributors should first think
about fixing the manual, then contribute to Worg. If fixing the
manual is possible (with the trade-off exposed above in mind), then
let's go for it. If it's beyond this trade-off and falls into Worg's
one, let's go for Worg.
> Where's the manual with respect to the new exporter? If it's ahead of
> Worg's state, the documentation on Worg can be used to supplement in
> reference to the manual vs. duplicating what's to come!
Nicolas, Thomas and I are working on it -- sorry it takes so long.
--
Bastien
next prev parent reply other threads:[~2013-04-08 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 4:51 Proposal for new/updated exporter tutorials on Worg John Hendy
2013-03-28 5:31 ` Thomas S. Dye
2013-03-28 10:37 ` Carsten Dominik
2013-03-28 12:35 ` John Hendy
2013-03-28 22:07 ` John Hendy
2013-03-30 13:45 ` Bastien
2013-04-01 4:58 ` John Hendy
2013-04-08 15:30 ` Bastien [this message]
2013-03-28 10:35 ` Carsten Dominik
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=87r4ik29xs.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
--cc=tsd@tsdye.com \
/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).