From: "Dominik, Carsten" <C.Dominik@uva.nl>
To: Bastien <bzg@altern.org>
Cc: Jarmo Hurri <jarmo.hurri@syk.fi>,
"<emacs-orgmode@gnu.org>" <emacs-orgmode@gnu.org>,
"Dominik, Carsten" <C.Dominik@uva.nl>
Subject: Re: [PATCH] Lookup functions, take two
Date: Tue, 25 Sep 2012 09:15:20 +0000 [thread overview]
Message-ID: <9C4C997C2CA6AA488CBC8C9E56E764EE11E75285@MBX04.uva.nl> (raw)
In-Reply-To: <87r4pqzxab.fsf@bzg.ath.cx>
Hi Bastien,
since you copied me, I guess you want my comment?
I think this is very useful functionality and I would vote for putting it into the core.
The documentation should be kept as compact as possible, I think without an example, just describe the functionality. Maybe Jarmo can write a little tutorial for Worg and document it there more extensively?
- Carsten
On 25.9.2012, at 03:49, Bastien wrote:
> Hi Jarmo,
>
> thanks for the explanations -- I should I've read your doc patch
> more closely.
>
> It is a nice spreadsheet utility function but my feeling is that
> having it in Org's core does not really fit, as it introduces
> functions where we usually have references. Functions are fine
> for users to add, though, that's the whole point of allowing
> Elisp in table formulas.
>
> Maybe I'm too conservative on this one. I will wait for other
> users' insight -- especially Carsten, who can better decide what
> fits and what does not in this area.
>
> Thanks,
>
> --
> Bastien
next prev parent reply other threads:[~2012-09-25 9:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 15:26 [PATCH] Lookup functions, take two Jarmo Hurri
2012-09-24 14:01 ` Bastien
2012-09-24 17:33 ` Jarmo Hurri
2012-09-25 1:49 ` Bastien
2012-09-25 4:13 ` Jarmo Hurri
2012-09-25 10:04 ` Bastien
2012-09-25 9:15 ` Dominik, Carsten [this message]
2012-09-25 10:02 ` Bastien
2012-09-26 13:00 ` Jarmo Hurri
2012-09-26 13:14 ` Bastien
2012-09-25 19:39 ` Achim Gratz
2012-09-25 22:43 ` Bastien
2012-09-26 13:45 ` Jarmo Hurri
2012-09-26 14:26 ` Bastien
2012-09-26 17:47 ` Jarmo Hurri
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=9C4C997C2CA6AA488CBC8C9E56E764EE11E75285@MBX04.uva.nl \
--to=c.dominik@uva.nl \
--cc=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=jarmo.hurri@syk.fi \
/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).