emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: [Babel] Preserving tabs in code blocks
Date: Fri, 26 Aug 2011 00:11:58 -0400	[thread overview]
Message-ID: <5393.1314331918@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bernt Hansen <bernt@norang.ca> of "Thu, 25 Aug 2011 21:13:21 EDT." <87mxex2cwe.fsf@norang.ca>

Bernt Hansen <bernt@norang.ca> wrote:

> Hi all,
> 
> I want to include the contents of a file which requires TABS between
> fields in a #+begin_src ... #+end_src block.
> 
> When I use C-c ' to edit the block the TABS are all converted back to
> spaces.  I want to be able to tangle the file and preserve the TABS
> which are required as input to some tool chain.
> 
> Is there some mode I can use to preserve the TABS?
> 
> For example:
> 
> #+begin_src fundamental :tangle testtabs.txt
> These	words
> are	separated
> by	tabs.
> #+end_src
> 
> I need to be able to create the testtabs.txt file with the TAB
> characters intact otherwise it fails as input to the tool chain (which I
> have no control over).
> 
> Is there any way to do this?
> 
> For now I'm keeping the input in a separate file, but I would much
> prefer to have it in a babel source block in my notes for future
> reference.
> 

Try setting org-src-preserve-indentation to t. If you change the default
value of indent-tabs-mode to nil (as I do), then you might have problems
in any case: inserted tabs will be changed to spaces. But if you have it
left at the default t, then I think this works.

Nick

  reply	other threads:[~2011-08-26  4:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26  1:13 [Babel] Preserving tabs in code blocks Bernt Hansen
2011-08-26  4:11 ` Nick Dokos [this message]
2011-08-26 10:14   ` Bernt Hansen

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=5393.1314331918@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bernt@norang.ca \
    --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).