From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Tangling takes long - profiling and calling R
Date: Tue, 16 Jun 2015 13:46:55 +0200
Message-ID: <87a8vzc1u8.fsf@selenimh.access.network>
References: <m2a8w12wni.fsf@krugs.de> <87ioaobvl1.fsf@selenimh.access.network>
	<m2lhfk0wn1.fsf@krugs.de>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58458)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Z4pJ2-0005JL-H2
	for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 07:45:29 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Z4pJ1-0006lU-JK
	for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 07:45:28 -0400
Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:40873)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1Z4pJ1-0006l4-DU
	for emacs-orgmode@gnu.org; Tue, 16 Jun 2015 07:45:27 -0400
In-Reply-To: <m2lhfk0wn1.fsf@krugs.de> (Rainer M. Krug's message of "Tue, 16
	Jun 2015 12:34:42 +0200")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org

Rainer M Krug <Rainer@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.

> 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?

Regards,