emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mario Frasca <mario@anche.no>
To: emacs-orgmode@gnu.org
Subject: tables, positioning of `#+Plot:' lines
Date: Fri, 5 Jun 2020 14:49:43 -0500	[thread overview]
Message-ID: <f798a70b-d64a-b3b1-a35e-a59f2c56e2f5@anche.no> (raw)

I was wondering about the position of the `#+plot:' lines.  we have a 
table, and if we want to have formulas, we put these in a `#+TBLFM:' 
line following the table.  the documentation of org-plot states that 
`#+PLOT:' lines are looked for: following, or preceding the table, but 
then only the "preceding" strategy is implemented.  I tried just out of 
curiosity, what happens if I put my `#+PLOT:' lines following the table 
but before the `#+TBLFM:' line.  in this case also the `#+TBLFM:' line 
is not found.

I see a couple of problems with this approach and in the current 

- only one single `#+TBLFM:' line is recognized, it must follow the 
table, there cannot be any other meta information in between the table 
and the `#+TBLFM:' line.

- other programs can't add meta information to the table, or must choose 
to stay after the `#+TBLFM:' line or before the `#+PLOT:' lines.

- you have meta information at the two ends of the table, instead of all 
on the same side.

I would like to implement the 'plot meta lines after the table', and 
some way to comment meta lines.

any thoughts?

my main doubt is that if we acknowledge meta lines at both ends, we end 
up with an unmanageable mess, where similar information can be very 
distant in the document.  I think it was a mistake to let PLOT 
directives be placed elsewhere than formulas, but I don't know if it's 
still worth changing this.

best regards, MF

             reply	other threads:[~2020-06-05 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05 19:49 Mario Frasca [this message]
2020-06-05 20:08 ` tables, positioning of `#+Plot:' lines Nicolas Goaziou
2020-06-05 20:16   ` Mario Frasca
2020-06-05 21:16     ` Nicolas Goaziou

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:

  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=f798a70b-d64a-b3b1-a35e-a59f2c56e2f5@anche.no \
    --to=mario@anche.no \
    --cc=emacs-orgmode@gnu.org \


* 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


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).