From: TEC <tecosaur@gmail.com>
To: Mario Frasca <mariotomo@inventati.org>
Cc: emacs-orgmode@gnu.org, Mario Frasca <mario@anche.no>
Subject: Re: WIP: Org-plot work
Date: Tue, 08 Sep 2020 11:21:41 +0800 [thread overview]
Message-ID: <87d02xc5ru.fsf@gmail.com> (raw)
In-Reply-To: <E1kFMHx-0006zm-Sx@lists.gnu.org>
Mario Frasca <mariotomo@inventati.org> writes:
> Hi all. Temporarily with hardly any connection. I dropped attempting
> to have my patches accepted after a couple of RFCs were met with
> silence. My understanding is that org-plot is abandoned, in favour of
> babel blocks, and I have too little interest in learning that.
Hi Mario! Good to hear from you,
I'm sorry to hear that your RFCs were met with silence - if it means
anything, had I been on the orgmode list at the time I likely would
have responded :)
I vaguely recall seeing that email saying that babel blocks should just
be used instead, and I fundamentally disagreed with the perspective of
the author. To me org-plot should be kept around, as gnuplot blocks can
not offer the same ease of functionality as org-plot. The default type
currently (pre my patches) were simple enough that they'd often be a few
lines, but org-plot has the ability to quickly create complex plots in a
concise manner which simply can't be matched by any other function in
org.
If no-one eles 'picks up the torch' with org-plot, I would like to do
so. Please give my patches a look/review, and consider bumping your RFCs
(so I have an email to reply to).
Thanks for your work,
Timothy.
next prev parent reply other threads:[~2020-09-08 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 18:54 WIP: Org-plot work Mario Frasca
2020-09-08 3:21 ` TEC [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-08 21:36 TEC
2020-07-30 5:17 ` TEC
2020-09-05 7:29 ` Bastien
2020-09-05 15:35 ` TEC
2020-09-06 5:34 ` Bastien
2020-09-06 5:39 ` TEC
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=87d02xc5ru.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mario@anche.no \
--cc=mariotomo@inventati.org \
/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).