From: Mario Frasca <email@example.com>
To: Kyle Meyer <firstname.lastname@example.org>
Subject: Re: [bug] select TODO items and unexpected behaviour
Date: Sun, 28 Jun 2020 09:53:33 -0500 [thread overview]
Message-ID: <email@example.com> (raw)
the "somehow", I can confirm it happened in the same session. it was
left like that when I ran toggle-debug-on-error and landed in the debugger.
I also noticed that the behaviour on the selection is only implemented
for some actions, not all.
if you select items, then S-<up> (to raise priority), the result is …
difficult to describe, non-selected parts of the buffer disappear, I am
asked about a Tag, for whatever reason, at this point I hit C-g, and the
raise-priority is applied, but only on the line containing the point.
went looking in the code for these functions, and the leading test,
recursively implementing the action on the selected lines, I only saw it
repeated with variations in a couple such functions. as said,
org-priority does not have it. I think the block could better be
generalized, my guess is by defining a well suited macro.
On 28/06/2020 01:32, Kyle Meyer wrote:
> Mario Frasca writes:
>> this behaviour comes after somehow my
>> `org-loop-over-headlines-in-active-region' became nil.
> Perhaps not the "somehow" but the default value of this option is
> different between the last release and master. It changed from nil to t
> in e360cd8f3 (Change the default values for several options,
>> if I set it back to t, I get the message "Symbol's value as variable is
>> void: right".
> Thanks for reporting. Looks like org-todo's call to org-map-entries has
> been broken since its introduction in 7.8.05. Should be fixed with
next prev parent reply other threads:[~2020-06-28 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 21:16 [bug] select TODO items and unexpected behaviour Mario Frasca
2020-06-27 21:43 ` Mario Frasca
2020-06-27 21:54 ` Mario Frasca
2020-06-28 6:32 ` Kyle Meyer
2020-06-28 14:53 ` Mario Frasca [this message]
2020-06-28 18:50 ` Mario Frasca
2020-06-28 20:06 ` Kyle Meyer
[not found] ` <firstname.lastname@example.org>
2020-06-28 20:04 ` Kyle Meyer
2020-06-27 22:46 ` Russell Adams
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).