[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Introduce "export features"
From: |
Sébastien Miquel |
Subject: |
Re: [PATCH] Introduce "export features" |
Date: |
Fri, 24 Feb 2023 12:51:00 +0000 |
Hi,
Timothy writes:
Notably, I’ve now got a draft manual entry (see the last patch attached), which
should go a long way to better explaining what this is without asking you to
wade through all the code comments 😄
Thank you for sharing your work Timothy, I've been using your export
features for a while.
I think it would be useful to support an easy way to toggle a feature
on and off. Either the manual should describe the best way to make a
feature depend on a user variable (this requires using the #+BIND
keyword, I guess), or I'd like org to support a new keyword, such as
: #+org_export_features
that would take a list of features, and enable them. Here, I am
thinking of features such as the `chikenize` example in the manual.
I have not tested it, but after a quick look at the patch, enabled
features should be available to the export transcoder functions,
through their =info= argument, aren't they ? This seems very useful.
--
Sébastien Miquel
- [PATCH] Introduce "export features", Timothy, 2023/02/10
- Re: [PATCH] Introduce "export features", Ihor Radchenko, 2023/02/11
- Re: [PATCH] Introduce "export features", Timothy, 2023/02/20
- Re: [PATCH] Introduce "export features",
Sébastien Miquel <=
- Re: [PATCH] Introduce "export features", Ihor Radchenko, 2023/02/24
- Re: [PATCH] Introduce "export features", Sébastien Miquel, 2023/02/24
- Re: [PATCH] Introduce "export features", Ihor Radchenko, 2023/02/26
- Re: [PATCH] Introduce "export features", Sébastien Miquel, 2023/02/26
- Re: [PATCH] Introduce "export features", Ihor Radchenko, 2023/02/27
- Re: [PATCH] Introduce "export features", Timothy, 2023/02/24
[POLL] Naming of "export features", Timothy, 2023/02/21