Re: [O] Referring to an Org Babel variable in the invocation arguments to another Org Babel code block

2017-01-01 Thread Zack Piper
Hi Nicolas, I tried "c", and it gives me: >>> c <<< as the result. I would like it to use the _variable_ "c", not the literal string. So the result should be ">>> test <<<" I've also cleaned up the Org I made (something went wrong when I pasted it before, it missed an #+END_SRC) Thanks! #+NAME:

Re: [O] Referring to an Org Babel variable in the invocation arguments to another Org Babel code block

2016-12-28 Thread Zack Piper
Hi all, Still struggling with this, does anyone have any ideas? Thanks! -- Zack Piper System administrator https://apertron.net

Re: [O] Referring to an Org Babel variable in the invocation arguments to another Org Babel code block

2016-12-27 Thread Zack Piper
Hi Charles, I think I found precisely the issue I'm having. When I use your example, and adjust it slightly: #+NAME: block-1 #+BEGIN_SRC shell :var x="X" echo ">>>" $x "<<<" #+END_SRC #+BEGIN_SRC shell :var c="test" y=block-1(c) echo $y #+END_SRC #+RESULTS:

[O] Referring to an Org Babel variable in the invocation arguments to another Org Babel code block

2016-12-27 Thread Zack Piper
ence ‘c’ not found in this buffer Org version: 9.0.3 Thanks! -- Zack Piper System administrator https://apertron.net

Re: [O] Concerning `(letrec ((ignore)) ...)' in line 2718 of lisp/ox.el

2015-12-11 Thread Zack Piper
On Fri, Dec 11, 2015 at 10:27:55AM -0500, Kyle Meyer wrote: > > Zack Piper writes: > > > I (think) I have a recipe to reproduce this: > > > > - Emacs 25 (emacs-25 branch from Git) > > - Org mode from latest Git (make sure that there's no ELC files from &

Re: [O] Concerning `(letrec ((ignore)) ...)' in line 2718 of lisp/ox.el

2015-12-11 Thread Zack Piper
I (think) I have a recipe to reproduce this: - Emacs 25 (emacs-25 branch from Git) - Org mode from latest Git (make sure that there's no ELC files from Emacs *24*, if it uses files from Emacs 24 it works fine (bug in byte compiler?)). ╭[ r.el ] │ (add-to-list 'load-path "~/org-mode/lisp"

[O] Concerning `(letrec ((ignore)) ...)' in line 2718 of lisp/ox.el

2015-12-10 Thread Zack Piper
Hi, When I attempt to export an Org document using the HTML backend (and Org backend) I get (after the initial tangle, even a normal Org document with the word "Example" fails): ╭ │ Wrong number of arguments: setq, 1 ╰ So I proceed to use Edebug to find out why this is happening: Line 2

Re: [O] org-mode fontification error

2015-12-10 Thread Zack Piper
> You haven't modified your load-path in this minimal config, so you're > using the built-in Org version, as indicated in your Org version output > above. That was it! Thanks! Sorry for the noise. -- Zack Piper http://apertron.net

Re: [O] "org-mode fontification error" on master

2015-12-10 Thread Zack Piper
Please refer to the second email I sent (14:35) as I feel this is better. Due to technical problems with my email system I sent two different ones and didn’t think to look in the logs, my apologies.

[O] org-mode fontification error

2015-12-10 Thread Zack Piper
(Apologies for the second email, didn’t see it go through...) When attempting to open an Org file (such as my own `config.org'), I get "org-mode fontification error" appear in the mini-buffer. I can reproduce it using the following: Org-mode version 8.2.10 (release_8.2.10 @ /home/zack/ins/share/

[O] "org-mode fontification error" on master

2015-12-10 Thread Zack Piper
re 'ob-tangle) │ (setq org-src-fontify-natively t) │ │ (find-file "~/.emacs.d/config.org") ╰ Which is loaded via: ‘emacs -Q -l r.el’ Emacs is also latest from the ‘emacs-25’ branch. Thanks! -- Zack Piper https://apertron.net

Re: [O] ox-latex doesn't export with `\newminted`.

2015-08-07 Thread Zack Piper
On Fri, Aug 07, 2015 at 03:22:32PM +0200, Rasmus wrote: > Zack Piper writes: > > > Apparently ox-latex doesn't add `\newminted` to languages that I wish > > to use. > > > > This is required to use: > > > > \begin{common-lispcode} > &g

[O] ox-latex doesn't export with `\newminted`.

2015-08-07 Thread Zack Piper
ld really be creating the corresponding environments automatically │ by default. But I would think it would really be simpler for it to │ export standard minted environments. I haven't used it, so I can't │ make any suggestions about configuration. ╰ Thanks! -- Zack Piper http://apertron.net