Skip to content

Conversation

natrys
Copy link
Contributor

@natrys natrys commented Aug 22, 2020

I think this fixes #136 . I believe the issue stemmed from the fact that elisp lists are passed by reference, not value, so a destructive operation on a function parameter here changed the original list passed to org-ql-search up the stack.

If nreverse was desired behaviour here, I can try some other way of fixing the linked issue.

@alphapapa alphapapa self-assigned this Aug 23, 2020
@alphapapa
Copy link
Owner

Thanks, this is probably the right way to fix it. I'll look at it and merge when I have time.

@alphapapa alphapapa force-pushed the master branch 2 times, most recently from e441d88 to 4194456 Compare November 9, 2020 02:07
@alphapapa alphapapa force-pushed the master branch 3 times, most recently from f52bef0 to ec0f8c7 Compare November 16, 2020 11:23
@alphapapa alphapapa added the bug label Nov 16, 2020
@alphapapa alphapapa added this to the 0.5 milestone Nov 16, 2020
@alphapapa
Copy link
Owner

Fixed in 29090c4 and 0.4.8.

@alphapapa alphapapa closed this Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

When multiple sorters are specified, something mutates the sorter list after first successful run

2 participants