emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Jonas Bernoulli <jonasbernoulli@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Something like #+BIND but for the destination buffer
Date: Tue, 3 Jan 2017 16:53:40 +0100	[thread overview]
Message-ID: <CA+7KPGfAN=g1LzfVJ3pxPSj3Tn1yH62h7SnQSaCiBEJ73-HmDA@mail.gmail.com> (raw)
In-Reply-To: <874m1krwk5.fsf@nicolasgoaziou.fr>

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

So here's the ECM:

* Node

#+BEGIN_SRC emacs-lisp
  (progn (progn foo
bar))
#+END_SRC

It doesn't matter whether `bar))` is preceded, in the org file, by two tabs
or 16 spaces. In both cases it will be preceded by one tab followed by 7
spaces in the texi file; and by 5 spaces followed by one tab followed by 6
spaces in the info file.

By the way, if I set `tabs-indent-mode` to `nil` in the org file, then tabs
are still used to indent code blocks. Is there a way to enforce the use of
spaces?

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

next prev parent reply	other threads:[~2017-01-03 15:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-31 14:17 Something like #+BIND but for the destination buffer Jonas Bernoulli
2016-12-31 14:40 ` 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 [this message]
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+7KPGfAN=g1LzfVJ3pxPSj3Tn1yH62h7SnQSaCiBEJ73-HmDA@mail.gmail.com' \
    --to=jonasbernoulli@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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

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