* [bug, ox or ob?] something leaks tabs in src blocks
@ 2015-10-26 14:23 Rasmus
2015-10-26 14:37 ` Nicolas Goaziou
0 siblings, 1 reply; 3+ messages in thread
From: Rasmus @ 2015-10-26 14:23 UTC (permalink / raw)
To: emacs-orgmode
Hi,
Consider the following example
* test
#+BEGIN_SRC R
test <- function(index, funs, ...){
if (missing(funs)) {
funs <- list(
"a" = funa,
"b" = funb)}
col <- vapply(funs, function(FUN) {
do.call(FUN, list(index, ...))}, 1.0)
col}
#+END_SRC
It includes no tabs. When exported with ox-latex or ox-ascii, but not
ox-html, it has become something along the following, which at least at
the time of posting contains tabs. When exporting via xelatex, tabs in
verbatim shows up as "^^I".
\begin{verbatim}
test <- function(index, funs, ...){
if (missing(funs)) {
funs <- list(
"a" = funa, # not really
"b" = funb,
"c" = func)}
col <- vapply(funs, function(FUN) {
do.call(FUN, list(index, ...))}, 1.0)
col <- pretty_num(col, rounding = TRUE)
names(col) <- names(funs)
col}
\end{verbatim}
Does anyone know WHERE tabs are introduced so I can try to fix this? It
seems by the time the src element reaches at least
org-export-format-code-default it already contains tabs.
Thanks,
Rasmus
--
El Rey ha muerto. ¡Larga vida al Rey!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bug, ox or ob?] something leaks tabs in src blocks
2015-10-26 14:23 [bug, ox or ob?] something leaks tabs in src blocks Rasmus
@ 2015-10-26 14:37 ` Nicolas Goaziou
2015-10-26 15:15 ` Rasmus
0 siblings, 1 reply; 3+ messages in thread
From: Nicolas Goaziou @ 2015-10-26 14:37 UTC (permalink / raw)
To: Rasmus; +Cc: emacs-orgmode
Hello,
Rasmus <rasmus@gmx.us> writes:
> Consider the following example
>
> * test
> #+BEGIN_SRC R
> test <- function(index, funs, ...){
> if (missing(funs)) {
> funs <- list(
> "a" = funa,
> "b" = funb)}
>
> col <- vapply(funs, function(FUN) {
> do.call(FUN, list(index, ...))}, 1.0)
> col}
> #+END_SRC
>
> It includes no tabs. When exported with ox-latex or ox-ascii, but not
> ox-html, it has become something along the following, which at least at
> the time of posting contains tabs. When exporting via xelatex, tabs in
> verbatim shows up as "^^I".
>
> \begin{verbatim}
> test <- function(index, funs, ...){
> if (missing(funs)) {
> funs <- list(
> "a" = funa, # not really
> "b" = funb,
> "c" = func)}
>
> col <- vapply(funs, function(FUN) {
> do.call(FUN, list(index, ...))}, 1.0)
> col <- pretty_num(col, rounding = TRUE)
> names(col) <- names(funs)
> col}
> \end{verbatim}
>
> Does anyone know WHERE tabs are introduced so I can try to fix this? It
> seems by the time the src element reaches at least
> org-export-format-code-default it already contains tabs.
This is to be expected if `org-src-preserve-indentation' is nil (since
you didn't use the i flag) and `indent-tabs-mode' is non-nil.
See also <http://permalink.gmane.org/gmane.emacs.orgmode/101768>.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [bug, ox or ob?] something leaks tabs in src blocks
2015-10-26 14:37 ` Nicolas Goaziou
@ 2015-10-26 15:15 ` Rasmus
0 siblings, 0 replies; 3+ messages in thread
From: Rasmus @ 2015-10-26 15:15 UTC (permalink / raw)
To: emacs-orgmode
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> This is to be expected if `org-src-preserve-indentation' is nil (since
> you didn't use the i flag) and `indent-tabs-mode' is non-nil.
Ah, indent-tabs-mode was set outside of the portion of my init.el that's
read when exporting async.
Thanks.
Rasmus
--
This is the kind of tedious nonsense up with which I will not put
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-10-26 15:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-26 14:23 [bug, ox or ob?] something leaks tabs in src blocks Rasmus
2015-10-26 14:37 ` Nicolas Goaziou
2015-10-26 15:15 ` Rasmus
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).