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

From: Bastien <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: ox-html: Bug or feature for export of title and meta information?
Date: Sun, 16 Feb 2020 11:44:27 +0100	[thread overview]
Message-ID: <875zg66cc4.fsf@gnu.org> (raw)
In-Reply-To: <87sgjbrk8l.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sat, 15 Feb 2020 15:35:54 +0100")

Hi Nicolas,

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> I don't think so. It is a constant, which may only matter when you write
> an export-backend. Its value is not even particularly important since
> any back-end can ignore it. Only its syntax really matters, as pointed
> out in, e.g., `org-export-define-derived-backend' docstring. To sum it
> up, I see it is an implementation detail.

I see, thanks.

> The manual might, however, be more rigorous about what keywords each
> back-end really interprets. I don't know how, and where, it could fit,
> tho.

I guess a tutorial on how to write a new export backend will give us a
hint on where and how to mention this. I am not sure it belongs to the
manual.

Best,

-- 
 Bastien

next prev parent reply	other threads:[~2020-02-16 10:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-21 12:20 ox-html: Bug or feature for export of title and meta information? Jens Lechtenboerger
2020-02-11  8:16 ` Bastien
2020-02-14 17:21   ` Jens Lechtenboerger
2020-02-14 19:31     ` Nicolas Goaziou
2020-02-14 19:38       ` Nicolas Goaziou
2020-02-14 20:47         ` Bastien
2020-02-15 14:35           ` Nicolas Goaziou
2020-02-16 10:44             ` Bastien [this message]
2020-02-15  7:45       ` Jens Lechtenboerger
2020-02-15 14:02         ` Nicolas Goaziou
2020-02-16 18:16           ` Jens Lechtenboerger
2020-02-17  9:47             ` Nicolas Goaziou
2020-02-17 18:32               ` Jens Lechtenboerger

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=875zg66cc4.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).