emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jonas Bernoulli <jonasbernoulli@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Something like #+BIND but for the destination buffer
Date: Sat, 31 Dec 2016 15:17:57 +0100	[thread overview]
Message-ID: <CA+7KPGf3W-L-_rnLT00PdBrBGHDDEaD8Wts9_LAuyJzk3L_=sQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]

I need to ensure that the texinfo exporter generates texi files that use
space for indentation even when the global value of indent-tabs-mode is t.
If tabs are used, then code blocks end up being intended wrong in the final
info file.

There are probably other more direct approaches to achieve this, but when I
stumbled into #+BIND I thought I had found the mechanism to achieve this.
But it turned out that #+BIND allows setting variables in the buffer from
which the export happens, not the buffer into which it happens. So I would
like to suggest the addition of something like #+BIND-DEST, to allow
setting variables in the destination buffer.

I could then use something like

#+BIND-DEST: indent-tabs-mode nil

# Local Variables:
# org-export-allow-bind-keywords: t
# End:

to ensure that indent-tabs-mode is disabled. Currently I am using this

(defun ox-texinfo+--disable-indent-tabs-mode
    (fn backend file-or-buffer
        &optional async subtreep visible-only body-only ext-plist
post-process)
  (let ((saved-indent-tabs-mode (default-value 'indent-tabs-mode)))
    (when (equal backend 'texinfo)
      (setq-default indent-tabs-mode nil))
    (unwind-protect
        (funcall fn backend file-or-buffer
                 async subtreep visible-only body-only ext-plist
post-process)
      (setq-default indent-tabs-mode saved-indent-tabs-mode))))

(advice-add 'org-export-to-file   :around
'ox-texinfo+--disable-indent-tabs-mode)
(advice-add 'org-export-to-buffer :around
'ox-texinfo+--disable-indent-tabs-mode)


Thanks for considering

[-- Attachment #2: Type: text/html, Size: 1980 bytes --]

             reply	other threads:[~2016-12-31 14:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 14:17 Jonas Bernoulli [this message]
2016-12-31 14:40 ` Something like #+BIND but for the destination buffer Nicolas Goaziou
2017-01-03 13:52   ` Jonas Bernoulli
2017-01-03 13:59     ` Kaushal Modi
2017-01-03 14:43       ` Thomas S. Dye
2017-01-03 14:59       ` Nick Dokos
2017-01-03 15:53   ` Jonas Bernoulli
2017-01-03 17:00     ` Charles C. Berry
2017-01-14 13:42       ` Jonas Bernoulli
2017-01-14 14:46         ` Nicolas Goaziou
2017-01-14 17:47           ` Jonas Bernoulli
2017-01-14 17:52             ` Nicolas Goaziou
2017-01-14 19:50               ` Jonas Bernoulli
2017-01-14 22:11               ` Jonas Bernoulli
2017-01-14 22:20                 ` Jonas Bernoulli
2017-01-14 21:48   ` Jonas Bernoulli

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='CA+7KPGf3W-L-_rnLT00PdBrBGHDDEaD8Wts9_LAuyJzk3L_=sQ@mail.gmail.com' \
    --to=jonasbernoulli@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).