From: Ihor Radchenko <yantar92@posteo.net>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>, Tom Gillespie <tgbugs@gmail.com>
Cc: Ypo <ypuntot@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: LIterate programming with calc (help)
Date: Tue, 01 Nov 2022 07:22:18 +0000 [thread overview]
Message-ID: <87sfj3i1g5.fsf@localhost> (raw)
In-Reply-To: <87tu3kb9ol.fsf@ucl.ac.uk>
"Fraga, Eric" <e.fraga@ucl.ac.uk> writes:
>> I guess that the main problem is that calc is tightly integrated with
>> interactive commands. Maybe ob-calc could be extended to somehow
>> indicate the commands to be executed in addition to inputting stack
>> entries.
>>
>> Not sure if there is much interest in such feature though.
>
> Thinking out loud, what would be better, but I have no idea how feasible
> it would be, would be to have ob-calc make use of the embedded calc
> functionality and syntax, so that you could write something like this:
>
> #+begin_src calc
> a := 300 m
> b := 2 a =>
> #+end_src
>
> which would output the result of any line with => on it.
I am CCing Tom Gillespie, the maintainer of ob-calc. Maybe he has
something to say.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-11-01 7:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 12:15 LIterate programming with calc (help) Ypo
2022-10-24 7:56 ` Fraga, Eric
2022-10-24 9:20 ` Ihor Radchenko
2022-10-24 9:51 ` Fraga, Eric
2022-10-24 11:43 ` Christian Moe
2022-10-24 11:26 ` Ypo
2022-10-24 15:25 ` Fraga, Eric
2022-10-31 9:23 ` Ihor Radchenko
2022-10-31 9:54 ` Fraga, Eric
2022-11-01 7:22 ` Ihor Radchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-26 20:16 Ypo
2023-09-10 13:06 Literate " Ypo
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=87sfj3i1g5.fsf@localhost \
--to=yantar92@posteo.net \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tgbugs@gmail.com \
--cc=ypuntot@gmail.com \
/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).