From: stardiviner <numbchild@gmail.com>
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 21:26:04 +0800 [thread overview]
Message-ID: <875zsyydn7.fsf@gmail.com> (raw)
In-Reply-To: <a34336db-0389-d4e9-8a7a-3e0c17a4e860@gmail.com>
Nikolay Kudryavtsev <nikolay.kudryavtsev@gmail.com> writes:
> Am I reading it correctly that C-c C-x C-r is no longer a valid keybinding? Is
> this the reason why it now behaves so stupidly, creating a block with :scope
> file and asking for that file? Can someone point me to a discussion of that
> change? Manual is still not updated about it and nothing in ORG-NEWS.
>
> Quickly using that key was quite useful to pop a clock report for a task and I
> really don't see why would anyone want to remove that.
I only added dispatcher for commands, but not modify command functions itself.
If I remember correctly, that commit indeed added changes in ORG-NEWS. So...
That's all I can say. I suggestion you check out Git log history with blame, to
figure what change that command behavior.
And don't be rude to people.
--
[ stardiviner ]
I try to make every word tell the meaning what I want to express.
Blog: https://stardiviner.github.io/
IRC(freenode): stardiviner, Matrix: stardiviner
GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
prev parent reply other threads:[~2019-03-04 13:26 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
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 [this message]
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=875zsyydn7.fsf@gmail.com \
--to=numbchild@gmail.com \
--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).