>>>>> Ihor Radchenko <yanta...@gmail.com> writes: > Colin Baxter 😺 <m43...@yandex.com> writes: >> What is the point of changing a default? Users can change to >> whatever they like, but a default is a default - i.e. remains >> fixed. Why a particular default arose belongs to peculiarities of >> history. Do people really want to revisit this year after year? >> The value of a default is irrelevant: what is important is that >> it does not change, once it is chosen, without some very good >> reason. I have not seen that reason in this particular case. The >> arguments of consistency are ephemeral.
> For some more context, other functions are not really consistent > about uppercase/lowercase: - =org-insert-structure-template= > lowercase - =org-insert-drawer= uppercase - > =org-insert-property-drawer= uppercase - > =org-babel-exp-code-template= defaults to uppercase - > =org-clock-find-position= defaults to uppercase :END: - > =org-feed-write-status= defaults to uppercase - > =org-inlinetask-insert-task= defaults to uppercase - > =org-mobile-write-agenda-for-mobile= defaults to uppercase - > =org-babel-examplify-region= lowercase > I just looked for END vs end. > So, unless there is overwhelming support for changing uppercase > defaults into lowercase and a thorough patch, I am inclined > towards preserving the existing behaviour. Agreed. > Changing just RESULTS keyword provides no benefit to making things > consistent. Agreed. Best - Colin