Envoyé de mon iPhone
> Le 16 juin 2015 à 13:46, Nicolas Goaziou <m...@nicolasgoaziou.fr> a écrit : > > Rainer M Krug <rai...@krugs.de> writes: > >> I would not remove it as even I have some org files using them - shame >> on me. > > We can check for that in Org Lint and warn the user. That would be a really good idea! > >> But what about making it user configurable? a variable >> ~org-babel-tangle-use-deprecated-header-args~ which if set to non-nil would >> enable this additional code, if nil it would be skipped? The default >> should be set to ~t~ to be backward compatible. > > This looks like backward-compatibility hell to me. If we make it > conditional the feature is no longer deprecated, is it? > > The more general question is: how many years do we need to wait before > removing a deprecated (i.e., marked as such) feature? Before deleting it, one should get a warning that a certain feature is deprecated. At the moment, it is only mentioned in the help (as far as I am aware). > > Regards,
