Re: [O] [BUG] org-sort-entries errors out when headline is empty

Hello, Sebastian Reuße writes: > As for my 5 cents on the (probably not too consequential) design issue: > I’d probably choose to treat this as an empty headline with tags. Due to > the special syntax, tags are “more special” than headlines, and my > expectation would be that

Re: [O] [BUG] org-sort-entries errors out when headline is empty

Hello Nicolas, Nicolas Goaziou writes: > Sebastian Reuße writes: >> I was also wondering if it might make sense to tweak >> ‘org-complex-heading-regexp’ so that the respective capture group >> captures an empty string. This could be achieved by making

Re: [O] [BUG] org-sort-entries errors out when headline is empty

Hello, Sebastian Reuße writes: > An alternative is to guard inside ‘org-sort-entries’. I’m following up with an > implementation of this. Applied. Thank you! I used `org-get-heading', which handles empty headlines without messing with `org-complex-heading-regexp'. > I was

[O] [BUG] org-sort-entries errors out when headline is empty

So, I’ve noticed that when sorting a subtree (alphabetically or numerically), ‘org-sort-entries’ will raise an error arising from the call to ‘org-sort-remove-invisible’ (lines 8761 and 8766 in bc7b24d0d). I’m following up with a test. The error is triggered by the capture group in