Tim Cross writes: > I can completely understand your position. However, I wanted to point > out that this change was documented in the org NEWS file, where all > version changes are documented. When upgrading to a new version of org, > everyone should look there, ideally before the upgrade or soon > afterwards and definitely when you notice some changed behaviour. It > will save hours of trouble shooting and often tells you how to restore > previous behaviour. A very under appreciated piece of valuable > documentation. I would like to agree, because I wish people would also read NEWS for my projects, but since I use at least 10-20 programs daily which depend on hundreds of libraries that might change their behavior, that’s unrealistic. I cannot read NEWS entries whenever my distro updates org-mode, therefore I depend on org-mode not breaking during updates. If an update changes behavior in a way that requires people to read up on stuff to find out how to continue working, that means that the program breaks with that update. I’ve been more liberal on that point before I saw the problems that arose from the Python2->Python3 transition. Many changes that each seem small on their own can cause significant damage, because there will always be some people that get hit by them during a period in their life when they cannot follow them, because they are fully occupied by work (mentally or because of little time) so the tools they trained with must just keep working. Best wishes, Arne -- Unpolitisch sein heißt politisch sein ohne es zu merken