Hi,
I'm having troubles getting more than one cell from an org table as a
variable in org-babel. Trying this example from the orgmode manual (
https://orgmode.org/manual/Environment-of-a-Code-Block.html):
#+NAME: example-table
| 1 | a |
| 2 | b |
| 3 | c |
| 4 | d |
#+BEGIN_SRC emacs-lisp :var d
John Mathena writes:
> First time sending mail to the list; please let me know if I commit any
> breaches of etiquette or convention (e.g. on attaching backtraces as a file
> vs sending in message body).
Your email is perfectly fine. Thanks for reporting and welcome to the
Org mailing list!
> I
Aloha all,
I pushed a new file, ob-doc-org.org, to Worg earlier today, but
the link in
https://orgmode.org/worg/org-contrib/babel/languages/index.html
gives a 404 error. I usually see this when the Org file has a bad
link that causes export to fail, but AFAICT ob-doc-org.org doesn't
have th
First time sending mail to the list; please let me know if I commit any
breaches of etiquette or convention (e.g. on attaching backtraces as a file
vs sending in message body).
I'll add a data point to the people that have been having trouble with
org-element--cache recently; I get the warning sho
I should also add I see the same error if I just run
#+BEGIN_SRC emacs-lisp
(org-org-export-as-org)
#+END_SRC
and I see the same behavior with an emacs -q session.
John
---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
If I run this block in an org file:
#+BEGIN_SRC emacs-lisp
(let ((org-export-before-parsing-hook '((lambda (_backend) nil
(org-org-export-as-org))
#+END_SRC
I get a traceback that starts with
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
goto-char(nil)
(if
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>>> If you are on main, you can just disable the warning, unless you start
>>> experiencing Emacs slowdown.
>>
>> I am on master (d4e192514769368e32c4e61629bf51e67a781bff)
>> I am confused.
>> Can I use org-transclusion, yes or no?
> Ye
Uwe Brauer writes:
>> If you are on main, you can just disable the warning, unless you start
>> experiencing Emacs slowdown.
>
> I am on master (d4e192514769368e32c4e61629bf51e67a781bff)
> I am confused.
> Can I use org-transclusion, yes or no?
Yes, you can.
> If I can which variable I have t
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> So what do you suggest
>>
>> - set a variable to nil, but which?
>>
>> - or wait to let Noboru fix the issue?
> If you are on main, you can just disable the warning, unless you start
> experiencing Emacs slowdown.
I am on master (d4e
Uwe Brauer writes:
> So what do you suggest
>
> - set a variable to nil, but which?
>
> - or wait to let Noboru fix the issue?
If you are on main, you can just disable the warning, unless you start
experiencing Emacs slowdown.
The warning you see is handled by org-element code correctly
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> I did run the check with the official org release and did *not* run into
>> any problem, so I presume it what Ihor says, the recent dev version.
> The official org release disables element cache by default. If you
> enable it, there wi
Uwe Brauer writes:
> I did run the check with the official org release and did *not* run into
> any problem, so I presume it what Ihor says, the recent dev version.
The official org release disables element cache by default. If you
enable it, there will be the same problem (but with no warning)
12 matches
Mail list logo
