From: Panayotis Manganaris <panos.manganaris@gmail.com>
To: Rens Oliemans <hallo@rensoliemans.nl>
Cc: emacs-orgmode@gnu.org, Richard H Stanton <rhstanton@berkeley.edu>
Subject: Re: How to specify column alignment in LaTeX table output?
Date: Fri, 10 Jan 2025 17:04:53 -0500 [thread overview]
Message-ID: <874j26pbp6.fsf@ASCALON.mail-host-address-is-not-set> (raw)
In-Reply-To: <87tta7vvtp.fsf@rensoliemans.nl>
Rens Oliemans <hallo@rensoliemans.nl> 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 move the #+ATTR_LATEX line above the table, Org mode will keep
> replacing that table on later code block evaluations (usually ;))
I intended to chime in here to share how the header-arg :post can be
used to avoid this inconvenience.
As it turns out, this is featured in the manual, and should work fine
for tables:
https://orgmode.org/manual/Results-of-Evaluation.html#Post_002dprocessing-1
Unfortunately, there appears to be trouble with using this method for
e.g. figures. I will open a new thread about this.
next prev parent reply other threads:[~2025-01-10 22:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 9:38 How to specify column alignment in LaTeX table output? Richard H Stanton
2025-01-09 10:17 ` Rens Oliemans
2025-01-09 15:02 ` Richard H Stanton
2025-01-10 9:47 ` Rens Oliemans
2025-01-10 9:53 ` Rens Oliemans
2025-01-10 22:04 ` Panayotis Manganaris [this message]
2025-01-10 16:59 ` Richard H Stanton
2025-01-10 18:59 ` Rens Oliemans
2025-01-10 19:16 ` Richard H Stanton
2025-01-10 19:38 ` Richard H Stanton
2025-01-10 19:45 ` Ihor Radchenko
2025-01-10 19:04 ` Richard H Stanton
-- strict thread matches above, loose matches on Subject: below --
2025-01-10 6:13 Pedro Andres Aranda Gutierrez
2025-01-10 17:04 ` Richard H Stanton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874j26pbp6.fsf@ASCALON.mail-host-address-is-not-set \
--to=panos.manganaris@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=hallo@rensoliemans.nl \
--cc=rhstanton@berkeley.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).