> On Jan 10, 2025, at 10:59 AM, Rens Oliemans wrote:
>
> Richard H Stanton writes:
>
>> Here’s an example:
>>
>> #+begin_src python :results output replace raw
>> print("a")
>> #+end_src
>>
>> Every time I run this code bloc
On Jan 10, 2025, at 10:59 AM, Rens Oliemans wrote:
>
> Richard H Stanton writes:
>
>> Here’s an example:
>>
>> #+begin_src python :results output replace raw
>> print("a")
>> #+end_src
>>
>> Every time I run this code block,
> On Jan 10, 2025, at 8:59 AM, Richard H Stanton wrote:
>
>>
>> On Jan 10, 2025, at 1:47 AM, Rens Oliemans wrote:
>>
>> Richard H Stanton writes:
>>
>>> what are the recommended headers for a Python code block that exports a
>>> t
On Jan 9, 2025, at 10:13 PM, Pedro Andres Aranda Gutierrez
wrote:
>
> Hi,
>
> For org tables generated in Python, I use python-tabulate. Actually, I forked
> the original library to include the possibility of generating the latex
> attributes from Python too.
>
> Something like:
>
> --- cut
> On Jan 10, 2025, at 1:47 AM, Rens Oliemans wrote:
>
> Richard H Stanton writes:
>
>> what are the recommended headers for a Python code block that exports a
>> table? For example, ":results output raw” and ":results output drawer” both
>> seem
On Jan 9, 2025, at 2:17 AM, Rens Oliemans wrote:
>
> Richard H Stanton writes:
>
>> Here’s a table in my org document:
>>
>> #+ATTR_LATEX: :align :options [htbp]
>> #+begin_table
>> |---++---+|
>&
Here’s a table in my org document:
#+ATTR_LATEX: :align :options [htbp]
#+begin_table
|---++---+|
| Tier | Number | Total | % of Total |
|---++---+|
| 1 | 4 | 8,700.00 | 57.39 |
| 2 | 19 | 5,398.00 |
I just tried to export a single subtree from an org document to a PDF file:
1) Type C-c C-e [org-export-dispatch]
2) C-s to narrow to subtree
3) l -> o to export to PDF via LaTeX
However, instead of exporting the portion of the file I want, I get the error
message
Undefined Org macro: newline;
I often create tables programatically from within an org code block. To make
sure I don’t produce multiple copies of the output, I like to enclose the
results in a drawer. However, the exporter seems to ignore any caption I might
assign if the table itself is inside a drawer. For example, if you
Commenting out the last line of init.el, thus not loading the beacon package,
gets things to work OK. But so does changing which version of org mode is
loaded by commenting out one of the lines and uncommenting the other, so this
is not only about the beacon package.
Best,
Richard
>
After a lot of bisecting my init.el to create the simplest possible example
that shows the problem, I found that removing the package beacon makes
everything work OK, both in sync and async mode.
> On May 19, 2022, at 6:37 AM, Ihor Radchenko wrote:
>
> Richard Stanton writes:
>
>> A bit mo
>> I’m creating documents where I run Python code blocks that create LaTeX
>> mathematical output that I want to be able to export to either LaTeX/PDF or
>> HTML.
>>
>> Using :wrap in the header works fine, except that LaTeX complains about the
>> unknown environment “results” (it still comp
12 matches
Mail list logo
