Thanks Bastien for all your work! --Diego On Fri, Feb 21, 2020 at 4:50 PM Bastien wrote: > Hi all, > > here are the results of the survey, with *47* voters: > > - 26+2 : org-loop-over-headlines-in-active-region => t > - 25+2 : org-agenda-loop-over-headlines-in-active-region => t > - 28+3 : org-fontify-done-headline => t > - 17+4 : org-hide-emphasis-markers => t > - 10+6 : org-hide-macro-markers => t > - 15+5 : org-refile-use-cache => t > - 23+6 : org-special-ctrl-k => t > - 20+6 : org-allow-promoting-top-level-subtree => t > - 22+5 : Add org-tempo to org-modules > > I've changed the values of these options in master: > > - 35+2 : org-src-tab-acts-natively => t > - 28+3 : org-fontify-done-headline => t > - 26+2 : org-loop-over-headlines-in-active-region => t > - 25+2 : org-agenda-loop-over-headlines-in-active-region => t > > I've *not* changed the values of these options: > > - 23+6 : org-special-ctrl-k => t > - 22+5 : Add org-tempo to org-modules > - 20+6 : org-allow-promoting-top-level-subtree => t > - 17+4 : org-hide-emphasis-markers => t > - 10+6 : org-hide-macro-markers => t > - 15+5 : org-refile-use-cache => t > > The reason for not changing the default of org-special-ctrl-k is that > 23 < 47/2. Also, I think it was a mistake to propose this: even the > org-special- prefix should have warned me. The org-special-* options > should be nil by default, and while org-special-ctrl-k may be useful, > it is as useful as org-special-ctrl-a/e, which sticks to nil too. > > The reason for not adding org-tempo to org-modules is, on top of the > poll being 22 < 47/2, that the current discussion on the list leaves > room for improvements that may lead to move org-tempo from Org's core > anyway. > > The reason for not changing the four other options is that they did > not get enough votes. > > I've push the change for the three options in current master. > > Thanks again for participating to the poll and to the discussions! > > Best, > > -- > Bastien > >