emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "David Lukeš" <dafydd.lukes@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Protect Org export from auto-formatting hooks
Date: Mon, 28 Feb 2022 14:23:20 +0100	[thread overview]
Message-ID: <87sfs33z1z.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAEPTPEyGmyGkE4rzakBQs_nfGJwtGuMs1YLmB7ar4bgW01OaVg@mail.gmail.com> ("David Lukeš"'s message of "Mon, 28 Feb 2022 14:14:36 +0100")


David Lukeš <dafydd.lukes@gmail.com> writes:

> Thanks, that's indeed a much better way of doing it :) One can even
> avoid the temp buffer altogether and write the `output' string
> directly with `(write-region output nil file)`.

Yup, even better.

> Shall I prepare a patch? Or would you rather do it yourself, since it
> was your idea?

Please be my guest. :)

Nicolas Goaziou

  reply	other threads:[~2022-02-28 13:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25 16:29 Protect Org export from auto-formatting hooks David Lukeš
2022-02-26  9:32 ` Nicolas Goaziou
2022-02-28 13:14   ` David Lukeš
2022-02-28 13:23     ` Nicolas Goaziou [this message]
2022-02-28 13:42       ` David Lukeš
2022-06-21 12:36         ` [PATCH] ox.el: Protect " David Lukes
2022-06-21 12:46           ` David Lukeš

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:

  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=87sfs33z1z.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=dafydd.lukes@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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