emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bastien <bzg@gnu.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org,
	=?utf-8?Q?Fran=C3=A7ois?= Pinard <pinard@iro.umontreal.ca>,
	"Nicolas Goaziou" <n.goaziou@gmail.com>
Subject: Re: "# <<tag>>" should stick to the following text
Date: Tue, 08 May 2012 10:33:17 +0200	[thread overview]
Message-ID: <87mx5jxeb6.fsf@altern.org> (raw)
In-Reply-To: <87sjfctvw2.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 7 May 2012 14:44:53 +0930")

Hi all,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> But maybe I also am confused as to the current direction this is
> taking...

let me try to summarize and clarify.  Nicolas said it clearly: 

  At the moment, "<<tag>>" and "# <<tag>>" produce, respectively, 
  "<a name="tag" id="tag">tag</a>" and "<a name="tag" id="tag"></a>".

Nothing is deprecated _yet_ and there is no need for a notice or an
update of the manual to this regard.  Quoting Nicolas again:

  In a not so distant future "<<tag>>" will produce "<a name="tag"
  id="tag"></a>" and "# <<tag>>" will be ignored.

So this *will* be deprecated when the new exporter will be part of 
Org's core.  We will update the manual by then.

Nicolas lives in the future because he's so much into the new exporter,
so that's why he said this *is* deprecated, but this isn't really yet.


Please keep testing the new exporters -- all contributions in this area 
help a lot with the development!

Thanks,

-- 
 Bastien

next prev parent reply	other threads:[~2012-05-08  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 20:35 "# <<tag>>" should stick to the following text François Pinard
2012-05-06 21:18 ` Nicolas Goaziou
2012-05-07  0:41   ` François Pinard
2012-05-07  1:44     ` François Pinard
2012-05-07  7:10     ` Nicolas Goaziou
2012-05-07  8:24       ` Eric S Fraga
2012-05-07 16:52       ` François Pinard
2012-05-08 14:14       ` Nick Dokos
2012-05-07  1:08   ` Nick Dokos
2012-05-07  5:14     ` Eric S Fraga
2012-05-08  8:33       ` Bastien [this message]
2012-05-07  5:34     ` Christian Moe

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=87mx5jxeb6.fsf@altern.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    --cc=nicholas.dokos@hp.com \
    --cc=pinard@iro.umontreal.ca \
    /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

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).