From: No Wayman <iarchivedmywholelife@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Introduce "export features"
Date: Sat, 11 Feb 2023 12:03:21 -0500 [thread overview]
Message-ID: <87lel4gm6b.fsf@gmail.com> (raw)
In-Reply-To: <mailman.13.1676134175.1258.emacs-orgmode@gnu.org>
> often we include content in export templates that is only
> relevant in
> particular situations.
>
> “export features” allow for the specification of qualities of
> the org buffer
> being exported that imply certain “features”, and how those
> features may be
> implemented in a particular export.
> now `\usepackage{svg}' is automatically added when exporting a
> buffer that
> includes SVG images.
> ┌────
> │ (org-export-update-features 'beamer
> │ (beamer-metropolis
> │ :condition (string-match-p \"metropolis$\" (plist-get info
> :beamer-theme))
> │ :snippet my-org-beamer-metropolis-tweaks
> │ :order 3))
> └────
As discussed on the Doom Emacs Discord, I strongly suggest
renaming to avoid overloading the term "feature".
To me, your description indicates sinppets are inserted
contextually.
Org has a similar notion of contexts with
`org-capture-templates-contexts'.
A similar name would be better as it does not overload the term
"feature", which already has a different meaning in elisp.
e.g. org-export-backend-contexts
next parent reply other threads:[~2023-02-11 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.13.1676134175.1258.emacs-orgmode@gnu.org>
2023-02-11 17:03 ` No Wayman [this message]
2023-02-10 17:20 [PATCH] Introduce "export features" Timothy
2023-02-11 11:37 ` Ihor Radchenko
2023-02-20 17:41 ` Timothy
2023-02-24 12:51 ` Sébastien Miquel
2023-02-24 12:59 ` Ihor Radchenko
2023-02-24 21:47 ` Sébastien Miquel
2023-02-26 12:19 ` Ihor Radchenko
2023-02-26 13:04 ` Sébastien Miquel
2023-02-27 19:05 ` Ihor Radchenko
2023-02-25 3:15 ` Timothy
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=87lel4gm6b.fsf@gmail.com \
--to=iarchivedmywholelife@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).