Re: [O] suppress leading ":" in org-babel output

Hello, Many thanks updating org-mode resolved the issue Best regards, Jeremie > FWIW, I just get the last line: > > #+NAME:mean_purchase_per_shopping_trip > > #+BEGIN_SRC R :var x=6 :results output :session *R* > a <-sprintf("%.2f",12.234324) > cat(a,sep="\n") > #+END_SRC > > #+RESULTS: > : 12.23

Re: [O] [PROPOSAL] Use prefix arg to control scope of org-narrow-to-subtree.

On 25 Apr 2019, Nicolas Goaziou wrote: >Hello, > >Karl Fogel writes: > >> My proposal is for each raw prefix arg (each `C-u' prefix) to expand >> the narrowing level outward/upward by one. So in the above situation: > >I suggest to use a numeric argument for that. M-1 for one level, M-2 for >two

[O] strange output when executing matlab using babel, strange ,

Hi I am running Ubuntu 16.06, matlab 2018b and I am using the python kernel to use matlab from within org mode Thanks to John Kitchin, I have the following setting * Lisp setting #+BEGIN_SRC emacs-lisp (setq org-confirm-babel-evaluate nil) ;don't prompt me to confirm everytime I want to

Re: [O] strange output when executing matlab using babel, strange ,

I believe you are seeing org's escaping at play. It puts a comma in front of the leading *. It must think that it is a heading in org-syntax, and so it escapes it to avoid some issues. I think here it is a bug since that is not a heading. can you use some other leading character? I don't think the

Re: [O] strange output when executing matlab using babel, strange ,

>>> "JK" == John Kitchin writes: > I believe you are seeing org's escaping at play. It puts a comma in front > of the leading *. It must think that it is a heading in org-syntax, and so > it escapes it to avoid some issues. > I think here it is a bug since that is not a heading. can you use some

Re: [O] strange output when executing matlab using babel, strange ,

Uwe Brauer writes: > Hi > > I am running Ubuntu 16.06, matlab 2018b and I am using the python > kernel to use matlab from within org mode > > > > * The problem > > When I run > > #+begin_src matlab :results output latex :exports results :eval never-export > disp('*Step 3:*') > disp('*St

Re: [O] strange output when executing matlab using babel, strange ,

> Uwe Brauer writes: > I don't think anything is wrong: org quotes lines that look like > headlines in the babel output by prepending the comma. But it shouldn't I want the output to be surrounded by * * because then it is exported to latex as \textbf smime.p7s Description: S/MIME

Re: [O] strange output when executing matlab using babel, strange ,

you are putting it in :results output latex though, so it won't be changed on export. The contents of that block will be used verbatim I think in the latex export. Maybe you can change latex to raw instead. Then the org syntax will get converted to \textbf. Otherwise, I think you have to put the l

Re: [O] [PATCH] Add :target option for the TOC keyword

Hello, Sacha Chua writes: > - catch the signal raised by org-export-resolve-fuzzy-link and then check for > the > special case of "local" > - always handle :target "local" as a local TOC > - or just leave the behaviour as it is. What would you recommend? The latter is fine. I applied you patc

Re: [O] suppress leading ":" in org-babel outputariBLE

AFAICS, the latest update (99aa984) did NOT fix the issue. There are complications in this story that I explain here. If I start a fresh *R* session by eval'ing the src block, I get #+RESULTS: : : 12.23 and the *R* buffer ends with --8<---cut here---start->

Re: [O] strange output when executing matlab using babel, strange ,

>>> "JK" == John Kitchin writes: > you are putting it in :results output latex though, so it won't be changed > on export. The contents of that block will be used verbatim I think in the > latex export. Maybe you can change latex to raw instead. Then the org > syntax will get converted to \textbf