Re: [O] How to treat string results of src-block calls like text in export?

t...@tsdye.com (Thomas S. Dye) writes: Hi Thomas, > I use this a lot in my work, but hadn't tried it in a headline. I tried > it with the call line in a headline and that works, too. This subtree > is in a file called personal.org. > > * Jolitz > > #+name: project-name > #+header: :exports none

Re: [O] How to treat string results of src-block calls like text in export?

Aloha Thorsten, Thorsten Jolitz writes: > t...@tsdye.com (Thomas S. Dye) writes: > > Hi Thomas, > >> Thorsten Jolitz writes: >> >>> Hi List, >>> >>> with this org file >>> >>> , >>> | #+name: project-name >>> | #+header: :exports none >>> | #+begin_src emacs-lisp >>> | (mapconcat >>> |

Re: [O] How to treat string results of src-block calls like text in export?

t...@tsdye.com (Thomas S. Dye) writes: Hi Thomas, > Thorsten Jolitz writes: > >> Hi List, >> >> with this org file >> >> , >> | #+name: project-name >> | #+header: :exports none >> | #+begin_src emacs-lisp >> | (mapconcat >> |'capitalize >> |(split-string >> | (file-name-nond

Re: [O] How to treat string results of src-block calls like text in export?

Aloha Thorsten, Thorsten Jolitz writes: > Hi List, > > with this org file > > , > | #+name: project-name > | #+header: :exports none > | #+begin_src emacs-lisp > | (mapconcat > |'capitalize > |(split-string > | (file-name-nondirectory > | (directory-file-name > | (f

[O] How to treat string results of src-block calls like text in export?

Hi List, with this org file , | #+name: project-name | #+header: :exports none | #+begin_src emacs-lisp | (mapconcat |'capitalize |(split-string | (file-name-nondirectory | (directory-file-name | (file-name-directory |(buffer-file-name (current-buffer) |