emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: manual: stale bindings for org-clock-report and org-columns-insert-dblock
Date: Mon, 04 Mar 2019 17:11:42 +0100	[thread overview]
Message-ID: <87imwyd3gh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <09ce6837-0e59-497e-8c01-0b2c1048116e@gmail.com> (Nikolay Kudryavtsev's message of "Mon, 4 Mar 2019 18:16:27 +0300")

Hello,

Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:

> The first is that drop in clock reports now use :scope file by
> default, instead of :scope subtree.

Indeed. This is because clocktable default properties include :scope
property. I removed it. Thank you.

> The second is that the clock report function is set up in some weird
> way that it gets broken if you use icicles. Gonna look into it
> further, not sure whether org or icicles is the bad actor here. The
> behavior I'm seeing is as follows:
>
> The command spawns empty table with :scope file, asks for a file, when
> I select that file, it asks for a function and I have no idea which
> function should I choose here.

I don't use Icicles, but I cannot reproduce it. What are the exact steps
to do so?

> The third is the removal of C-c C-x C-r. I've read the discussion
> there, but it seems like nobody really wanted it removed, this is just
> a  consequence of refactoring. So, can we get C-c C-x C-r
> org-clock-report back, if only as a closure over
> org-dynamic-block-insert-dblock?

I don't see the need for that. You can, however, bind `C-c C-x C-r' to
`org-clock-report' in your config.

> Also, ever since that Stardiviner's commit the dynamic reloading of
> org seems to be broken on master. When I try to I get:
>
> Symbol’s function definition is void: org-dynamic-block-define

You seem to have a mixed installation. This function only exists in
development branch, i.e., Org 9.3, not ELPA.

> Another thing, since org is moving towards unifying dynamic blocks,
> maybe the next step is to add begin_src blocks into the mix in
> org-dynamic-block-insert-dblock? It seems that they historically have
> different syntax, but are in practice the same thing. That's actually
> one place where I could use a wizard.

My practice differs. I don't see them as the same thing. Their syntax is
vaguely related, but that's all.

Note you can insert source blocks with 'C-c C-,`

> And why the function is called org-dynamic-block-insert-dblock and not
> org-insert-dblock? Seems redundant to me.

Hysterical raisins, I assume.

> Also can someone explain how do I get from org elpa version to the git
> commit it's based on? E. g., in org-version.el I have
> "9.2.1-33-g029cf6-elpaplus" but g029cf6 does not seem like a real
> commit in the git repo.

Drop the "g". The relative commit is "029cf6".

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-03-04 16:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-11  2:19 manual: stale bindings for org-clock-report and org-columns-insert-dblock Kyle Meyer
2019-01-11 11:37 ` stardiviner
2019-03-03 15:44 ` Nikolay Kudryavtsev
2019-03-03 17:14   ` Kyle Meyer
2019-03-04 15:16     ` Nikolay Kudryavtsev
2019-03-04 16:11       ` Nicolas Goaziou [this message]
2019-03-05  1:51         ` Nikolay Kudryavtsev
2019-03-09 20:09         ` Nikolay Kudryavtsev
2019-03-10 20:52           ` Nicolas Goaziou
2019-05-07 15:40             ` Nikolay Kudryavtsev
2019-03-04 18:32       ` Nick Dokos
2019-03-04 13:26   ` 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=87imwyd3gh.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=nikolay.kudryavtsev@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).