From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thierry Banel <tbanelwebmin@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Feature Request] Add an dispatcher command (keybinding) for inserting dynamic blocks
Date: Sun, 25 Nov 2018 11:09:43 +0100 [thread overview]
Message-ID: <87wop1zcwo.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <3332dc93-afb1-0854-6298-06e0939aff3a@free.fr> (Thierry Banel's message of "Fri, 16 Nov 2018 18:59:42 +0100")
Hello,
Thierry Banel <tbanelwebmin@free.fr> writes:
> Org defines C-c C-x i as org-insert-columns-dblock. Instead, it could call the org-insert-dblock dispatcher shown here. The original org-insert-columns-dblock would be one among
> other dblock inserters.
>
> Possible dblocks:
> org-insert-columns-dblock
> org-clock-report
> propview
> invoice
> org-insert-dblock:aggregate
> org-insert-dblock:join
> org-insert-dblock:transpose
>
> Any future dblock inserter would be taken into account by the
> dispatcher just by providing an autoloadable
> org-insert-dblock:something function.
I think we could do something similar to links, i.e., populate
a variable (for links, it is `org-link-parameters') with a command
(`org-link-set-parameters'), so the dispatcher knows what dynamic blocks
can be provided.
Otherwise, it sounds like a good idea.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-11-25 10:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-16 1:15 [Feature Request] Add an dispatcher command (keybinding) for inserting dynamic blocks stardiviner
2018-11-16 17:59 ` Thierry Banel
2018-11-25 10:09 ` Nicolas Goaziou [this message]
2018-12-03 6:43 ` stardiviner
2018-12-20 2:10 ` stardiviner
2018-12-22 22:54 ` Nicolas Goaziou
2018-12-23 6:26 ` stardiviner
2018-12-23 6:28 ` stardiviner
2018-12-23 7:59 ` stardiviner
2018-12-27 10:59 ` Nicolas Goaziou
2018-12-27 15:25 ` stardiviner
2018-12-30 9:27 ` Nicolas Goaziou
2019-01-02 0:12 ` stardiviner
2019-01-02 14:57 ` Nicolas Goaziou
2019-01-03 12:19 ` stardiviner
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=87wop1zcwo.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=tbanelwebmin@free.fr \
/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).