From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Mario Frasca <mario@anche.no>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] allow for multiline headers
Date: Wed, 01 Jul 2020 12:46:49 +0200 [thread overview]
Message-ID: <87eepvfr6u.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <02a9b6b7-589d-bd19-28bb-5293441f4b04@anche.no> (Mario Frasca's message of "Mon, 29 Jun 2020 17:01:08 -0500")
Hello,
Mario Frasca <mario@anche.no> writes:
> IMO, we are keeping org-plot artificially basic.
Exactly.
There are multiple ways to draw a diagram from a table. One could use
gnuplot, or asymptote, or R, or, matplotlib… From a design point of
view, there is no particular reason to favor one way or the other, and
I don't see how Org Plot could fit to handle all of these. OTOH, Babel
source code blocks handle all of them.
I didn't check but I think Org Plot predates Org Babel. It probably
wouldn't exist otherwise.
> But you know what?
> I'm just happy with my additions, my point was to share them with the
> wider public. I can also keep my own branch in my own repository.
> I'm fine either way. When solving conflicts will become a burden,
> I'll write again to the list.
>
> I haven't yet delved into Babel code blocks. I would need to write
> code, isn't it? Now I just need defining settings. … sounds easier,
> so I'll keep it this way, here on my PC at least.
I don't know if there's much difference between writing multiple PLOT
lines and writing a gnuplot script. It may be interesting to compare use
cases.
Also, note that when you suggest something like PLOT[0] and PLOT[1], you
are effectively suggesting to write code, with conditionals.
Anyhow, I think it is more future-proof to use, and possibly improve
"ob-gnuplot.el" so it is easier to use, than to develop PLOT keywords.
WDYT?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2020-07-01 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 17:14 [PATCH] allow for multiline headers Mario Frasca
2020-06-12 22:44 ` Nicolas Goaziou
2020-06-13 20:20 ` Mario Frasca
2020-06-13 21:20 ` Mario Frasca
2020-06-13 22:18 ` Nicolas Goaziou
2020-06-13 23:03 ` Mario Frasca
2020-06-14 19:23 ` Nicolas Goaziou
[not found] ` <3e6ee551-4ef7-7d96-93dc-19a4973e1af8@anche.no>
[not found] ` <871rm5vslh.fsf@nicolasgoaziou.fr>
2020-06-27 15:39 ` Mario Frasca
2020-06-28 23:17 ` Nicolas Goaziou
2020-06-29 0:27 ` Mario Frasca
2020-06-29 12:50 ` Nicolas Goaziou
2020-06-29 16:26 ` Mario Frasca
2020-06-29 18:36 ` Nicolas Goaziou
2020-06-29 22:01 ` Mario Frasca
2020-07-01 10:46 ` Nicolas Goaziou [this message]
2020-07-01 12:06 ` Mario Frasca
2020-07-04 8:58 ` Nicolas Goaziou
2020-07-04 13:47 ` Mario Frasca
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=87eepvfr6u.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mario@anche.no \
/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).