From: Kyle Meyer <firstname.lastname@example.org>
To: Daniele Nicolodi <email@example.com>
Cc: Org Mode List <firstname.lastname@example.org>
Subject: Re: [PATCH] doc/org-manual.org: Extend table formulas Lisp form documentation
Date: Fri, 27 Nov 2020 01:40:44 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
Daniele Nicolodi writes:
> On 25/11/2020 05:37, Kyle Meyer wrote:
>> Daniele Nicolodi writes:
>>> Would it be worth to mention org-sbe in the same section of the manual?
>> Yeah, it looks like there's no mention of org-sbe in the manual, so I
>> think so (as a separate patch).
> After playing a bit with org-sbe, I came to the conclusion that it is
> broken beyond repair, at least without breaking it for the people that
> managed to make it work for them.
> I think that adding mention of it in the manual and explain all the
> quirks of the macro is much more work than replace it with something
Okay. org-sbe isn't something I've ever used, and I only have a
superficial understanding of it.
> I tried to write a better macro, please have a look here:
> and the parent message for an explanation of what I think is broken in
> org-sbe. Would you support adding org-sbx (for a lack of a better name)
> to ob-table.el and mention it in the manual instead of org-sbe? I would
> not go as far as deprecating org-sbe, just yet, but maybe soon...
Sorry, I haven't got around to looking at that thread yet (though
ideally someone that knows more about org-sbe will chime in).
> Subject: [PATCH] doc/org-manual.org: Extend table formulas Lisp form
> doc/org-manual.org (Emacs Lisp forms as formulas): Be more
> explicit about how fields are interpolated into the Lisp forms,
> clarify the use of mode flags, and add a couple more examples.
Thanks for the update. Applied (b2d38a822), adding an asterisk before
prev parent reply other threads:[~2020-11-27 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 18:06 [PATCH] doc/org-manual.org: Extend table formulas Lisp form documentation Daniele Nicolodi
2020-11-16 10:25 ` Eric S Fraga
2020-11-16 10:51 ` Daniele Nicolodi
2020-11-16 12:35 ` Tim Cross
2020-11-18 19:42 ` TEC
2020-11-18 20:15 ` Charles Millar
2020-11-25 4:37 ` Kyle Meyer
2020-11-25 20:44 ` Daniele Nicolodi
2020-11-27 6:40 ` Kyle Meyer [this message]
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 \
* 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).