emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.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: Sat, 30 Mar 2013 14:45:37 +0100	[thread overview]
Message-ID: <87y5d5ypa6.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CA+M2ft8S0HCGbuikP5OrdvYmDqwEzsiN779pLoaa3s9bMAUddw@mail.gmail.com> (John Hendy's message of "Thu, 28 Mar 2013 17:07:59 -0500")

Hi John,

thanks for the great work so far!  This is of huge help.

John Hendy <jw.hendy@gmail.com> writes:

> My thinking on this is that Org-8.0 is a significant step, however it
> would be nice to write documentation as it pertains to Org 8.0 and not
> constantly in reference to how it's different from Org-7.x.

Agreed.  If there is no indication on the Worg page, users should be
right in assuming this is for the latest stable version.

Instead of an "OUTDATED" cookie, I suggest introducing 

  #+PROPERTY: OrgCompat_ALL 8.0 7.9 7.8 7.7

(... using values from `customize-package-emacs-version-alist')

in a setup file and

  #+PROPERTY: OrgCompatible 8.0

in files where instructions are relevant starting from 8.0.

Then a macro could insert that compatible version.

What do you think?

-- 
 Bastien

  reply	other threads:[~2013-03-30 13: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 [this message]
2013-04-01  4:58           ` John Hendy
2013-04-08 15:30             ` Bastien
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=87y5d5ypa6.fsf@bzg.ath.cx \
    --to=bzg@altern.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).