From: Nick Dokos <nicholas.dokos@hp.com>
To: Vladimir Lomov <lomov.vl@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Problem with exporting TAB key
Date: Thu, 05 Apr 2012 00:13:10 -0400 [thread overview]
Message-ID: <3418.1333599190@alphaville> (raw)
In-Reply-To: Message from Vladimir Lomov <lomov.vl@gmail.com> of "Thu, 05 Apr 2012 11:10:11 +0900." <CAKwiCqtnW_JutMJSQg+S9wzn=33_f-7chnsmJtOZ-78sR_iznA@mail.gmail.com>
Vladimir Lomov <lomov.vl@gmail.com> wrote:
> #+TITLE: Problem with exporting TAB key
> #+AUTHOR: Vladimir Lomov
>
> * How to make TAB key to be exported from ORG document?
>
> Consider the following example:
> #+name: ex1
> #+BEGIN_SRC sh :exports code
> sort -t " " -k 3 -o file2 file1
> sort -t " " -k 3 -o file3 file
> #+END_SRC
>
> How I inserting the TAB key in example: for first line I use =C-q
> C-I=, for second line I use =C-q TAB=, but in tangled file and in
> exported HTML document it is NOT a TAB just spaces.
>
> How to force export and tangle functions not to convert TAB to spaces?
>
You can't: org-export-preprocess-string (in lisp/org-exp.el) contains a
call to untabify:
(untabify (point-min) (point-max))
which converts tabs to spaces, no questions asked. I don't know why that
is, so maybe Bastien or Carsten can tell us the reason.
If you are feeling adventurous, you might want to try commenting out
that call and see what, if anything, breaks.
Nick
> * COMMENT
>
> #+BEGIN_SRC sh :tangle ex.sh :shebang "#!/bin/bash" :noweb yes
> <<ex1>>
> #+END_SRC
>
next prev parent reply other threads:[~2012-04-05 4:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 2:10 Problem with exporting TAB key Vladimir Lomov
2012-04-05 4:13 ` Nick Dokos [this message]
2012-04-05 4:43 ` Vladimir Lomov
2012-04-05 5:01 ` Olaf Meeuwissen
2012-04-05 5:27 ` Vladimir Lomov
2012-04-06 1:34 ` Vladimir Lomov
2012-04-06 9:11 ` Bastien
2012-04-06 14:03 ` Vladimir Lomov
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=3418.1333599190@alphaville \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=lomov.vl@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).