From: Mart van de Wege <mart@vdwege.eu>
To: "Juan Manuel Macías" <maciaschain@posteo.net>,
"Mart van de Wege" <mvdwege@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: Inserting LaTex expressions using a filter fails
Date: Wed, 06 Jan 2021 16:17:21 +0100 [thread overview]
Message-ID: <69c1bfe1728883e982ee09c7cc341e2935a0df48.camel@vdwege.eu> (raw)
In-Reply-To: <878s96z208.fsf@posteo.net>
On Wed, 2021-01-06 at 13:24 +0100, Juan Manuel Macías wrote:
> Mart van de Wege <mvdwege@gmail.com> writes:
>
> > Kind of weird it's not mentioned in the docs though (at least not
> > in
> > the same section as export filters); if you're going to tell people
> > that
> > you can bind local functions to an org file, then it might be nice
> > to
> > point out that you do need to turn that on.
>
> You're right. I think an addition could be proposed in the
> documentation: for example, a footnote in the section `Defining
> filters
> for individual files', since by default the variable
> `org-export-allow-bind-keywords' has value nil.
You're right. I looked up the variable, and there is only one mention
in the docs, and that is about binding emacs variables locally to the
org file buffer.
Can I just clone the repo and prepare a patch?
Regards,
Mart van de Wege
next prev parent reply other threads:[~2021-01-06 18:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 18:33 Inserting LaTex expressions using a filter fails Mart van de Wege
2021-01-05 21:58 ` Juan Manuel Macías
2021-01-06 7:50 ` Mart van de Wege
2021-01-06 11:51 ` Juan Manuel Macías
2021-01-06 12:00 ` Mart van de Wege
2021-01-06 12:24 ` Juan Manuel Macías
2021-01-06 15:17 ` Mart van de Wege [this message]
2021-01-06 15:58 ` Juan Manuel Macías
2021-01-06 16:00 ` Mart van de Wege
2021-01-05 22:31 ` Nick Dokos
2021-01-06 7:50 ` Mart van de Wege
2021-01-06 15:48 ` Maxim Nikulin
2021-01-06 17:56 ` Mart van de Wege
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=69c1bfe1728883e982ee09c7cc341e2935a0df48.camel@vdwege.eu \
--to=mart@vdwege.eu \
--cc=emacs-orgmode@gnu.org \
--cc=maciaschain@posteo.net \
--cc=mvdwege@gmail.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).