Re: [bug] select TODO items and unexpected behaviour

[Mario Frasca]

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.

regards, MF

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,
> 2020-02-21).
>
> > 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
> 8a2eb7d1b.