While trying to set up a toy example for another thread, I stumbled into
a problem. It's been over a year since I did this, but I recall it was
possible to use multiple :results format values e.g.
:results output file link drawer
Using both link and drawer was acceptable with Emacs 28.2 Org mode
Rens Oliemans writes:
> Ah, here we see the exact problem we've both just attested to! The #+RESULTS:
> code block
> got recreated because I was messing around with ':results' headers, and the
> #+ATTR_LATEX:
> line doesn't belong to the correct table anymore.
>
> You will notice that if you mo
Hi all,
I have two small improvement suggestions for org-timer, and would like to hear
your thoughts.
1. I use org-timer to run pomodoro-style clocks. When the timer finishes, I
would like to generate a log entry. It would be helpful to be able to access
the duration of the clock; however, in
Richard H Stanton writes:
>>#+begin_src python :results output latex
>> print("a")
>>#+end_src
>>
>>#+RESULTS:
>>#+begin_export latex
>>a
>>#+end_export
>>
>> This is more or less what you had with your flushleft drawer, so I'm not sure
>> whether this fixes anythin
> 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, I get another line containing “a”. If I
>> don't use the raw o
Karthik Chikmagalur writes:
> Currently the value of `org-image-align' or of the `:align' attr_*
> keyword is respected when previewing images in the following two
> situations:
>
> 1. Image link in its own paragraph:
>
> #+attr_org: :align center
> [[file:/path/to/image.png]]
>
> 2. Image link a
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, I get another line containing “a”. If I
>> don't use the raw optio
> 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
>>> table? For example, ":results output raw” and ":results output
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, I get another line containing “a”. If I
> don't use the raw option, e.g.,
>
> #+begin_src python :results output
> print("a")
> #+end_
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 to work (without :wrap), while “:results outp
The holidays got the better of me and I'm just coming back to this. I've
made the code changes to add the new function for resolving the base name,
but I was thinking about adding a test for it as well. I'm looking at the
examples in test-ob-tangle.el and I think I understand some of it, but is
the
Response below/inline for email Emily Bourke wrote:
> (original email sent 10 Jan 2025 at 09:25)
>
> Is there a way in org to have timestamps with both a repeater and an end date?
No, there isn't.
The recommended way to achieve what you want is to create an entry for
the first occurrence and the
Hi,
Is there a way in org to have timestamps with both a repeater and an end date?
I tried <2024-11-29 Fri 11:30-12:00 +2w>--<2025-01-10 Fri>, intending that to
mean “11:30-12:00, every two weeks, starting on 2024-11-29 and ending on
2025-01-10”, but it seems org mode (org-version 9.7.11) inter
Rens Oliemans writes:
>
> #+RESULTS:
> |---++---+|
> | Tier | Number | Total | % of Total |
> |---++---+|
> | 1 | 4 | 8,022.65 | 65.45 |
> | 2 | 19 | 1,549.71 | 12.64 |
> | 3 | 24 | 2,685.28
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 to work (without :wrap), while “:results output” puts everything in an
> example block, which then seems to g
16 matches
Mail list logo