This makes sense to me. I agree about keeping things simple for now (I'm assuming it's not that common to mix priority ranges with included files). Looking through my notes I think we've covered all of the outstanding findings around numeric priorities. Should we close out this issue in Woof for now? We can always open a new one if something comes up that needs work.
Cheers, Derek On Sat, Feb 28, 2026 at 6:02 AM Ihor Radchenko <[email protected]> wrote: > "Jacob S. Gordon" <[email protected]> writes: > > >>> #+OPTIONS: pri:t > >>> #+PRIORITIES: 1 3 2 > >>> * TODO [#5] Task > >>> * TODO [#2] Task > > > > Even though there’s no ambiguity about the limits, you could argue > > the intermediate buffer is still invalid (e.g., fails ‘org-lint’). > > Invalid Org buffers do not exist :) Any plain text buffer is a valid Org > buffer. > > The only question is whether an Org buffer expresses what the user wants > to express. But in the above example, there is an ambiguity - does the > user really want to use 1-5 priority range? Or is it 1-3 and the > incompatibility is overlooked? Or maybe #1, #2, #3 in one buffer should > be transformed into #1, #3, and #5 with priorities changing to > 1,2,3,4,5? There is no general answer to this question other than asking > user to be more specific. > > In the current state, Org uses a very simple approach to resolve > ambiguities - first keyword "wins". Another way it doing something more > sophisticated, but IMHO even very sophisticated handing of multiple > keywords will still run into edge cases and do something other than what > user wants. Yet, too complex defaults may also confuse users. So, I'd > rather keep the defaults simple unless we can justify going into > complications. > > -- > Ihor Radchenko // yantar92, > Org mode maintainer, > Learn more about Org mode at <https://orgmode.org/>. > Support Org development at <https://liberapay.com/org-mode>, > or support my work at <https://liberapay.com/yantar92> > -- +---------------------------------------------------------------+ | Derek Chen-Becker | | GPG Key available at https://keybase.io/dchenbecker and | | https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org | | Fngrprnt: EB8A 6480 F0A3 C8EB C1E7 7F42 AFC5 AFEE 96E4 6ACC | +---------------------------------------------------------------+
