From: Linus Arver <linusarver@gmail.com>
To: emacs-orgmode@gnu.org
Cc: hniksic@xemacs.org
Subject: Re: including files and org-src-preserve-indentation
Date: Fri, 20 Feb 2015 19:27:18 -0800 [thread overview]
Message-ID: <20150221032716.GA12319@k0> (raw)
In-Reply-To: <87oaovjcv6.fsf@nicolasgoaziou.fr>
On Sun, Feb 15, 2015 at 06:36:29PM +0100, Nicolas Goaziou wrote:
> Hello,
>
> Linus Arver <linusarver@gmail.com> writes:
>
> >> When I call org-publish-current-project, the included file's TAB
> >> characters automatically become converted into spaces. Is there an
> >> orgmode way of preventing this auto-conversion?
>
> I cannot reproduce it. Could you provide an ECM?
So, after I created a minimal complete example (ECM), I loaded in the
latest org-mode (Git HEAD) and realized that the problem does not exist
in Org. It is with the `htmlize` [1] package. That is, if I simply
uninstall that package from my MELPA folder, the tabs stay as tabs,
regardless of what version of Org (latest Git HEAD or 8.2.10) I use.
> Also, what happens if
> you do a regular export (no publishing)?
If I call `org-html-export-to-html`, I get the same behavior. I.e., if I
have `htmlize` installed, the tabs get converted into spaces. If I
remove `htmlize`, the tabs are preserved nicely.
I would file a bug report upstream, but it appears that `htmlize` does
not have a website. It looks like the official version of `htmlize` [2]
has "untabify" (grep it) hardcoded into the program, so a quick fix may
not be in order any time soon.
Meanwhile from the Org side, perhaps we can have a way to let the user
select which program to use for syntax highlighting? Maybe something
external like Pygments [3]?
It would be helpful if Org could tell the user that it found (or did not
find) the `htmlize` package and that it was used (or not used) when
calling either `org-publish-current-project` or
`org-html-export-to-html`.
-L
[1]: http://melpa.org/#/htmlize
[2]: http://fly.srk.fer.hr/~hniksic/emacs/htmlize.el.cgi
[3]: http://pygments.org/
next prev parent reply other threads:[~2015-02-21 3:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 0:34 including files and org-src-preserve-indentation Linus Arver
2015-02-08 5:32 ` Linus Arver
2015-02-15 17:36 ` Nicolas Goaziou
2015-02-21 3:27 ` Linus Arver [this message]
2015-02-21 5:10 ` Linus Arver
2015-03-10 8:35 ` Nicolas Goaziou
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=20150221032716.GA12319@k0 \
--to=linusarver@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hniksic@xemacs.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).