From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Tangling takes long - profiling and calling R
Date: Tue, 16 Jun 2015 14:45:48 +0200 [thread overview]
Message-ID: <vriu616nrfcz.fsf@example.com> (raw)
In-Reply-To: 87a8vzc1u8.fsf@selenimh.access.network
Nicolas Goaziou <mail-Gpy5sJQTEQHwkn9pgDnJRVAUjnlXr6A1@public.gmane.org> writes:
> Rainer M Krug <Rainer-vfylz/Ys1k4@public.gmane.org> writes:
>
>> I would not remove it as even I have some org files using them - shame
>> on me.
To be clear, are we talking of constructs such as:
--8<---------------cut here---------------start------------->8---
** Subtree
:PROPERTIES:
:tangle: no
:END:
--8<---------------cut here---------------end--------------->8---
?
> 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?
I understand your point, and I'm enclined to agree with you (for
a long-term sanity and stability of the mode we all cherish) -- even if
I dunno yet if I still use such (Well, if this is the above structure,
then, yes, I use it a lot as well...).
> The more general question is: how many years do we need to wait before
> removing a deprecated (i.e., marked as such) feature?
Your suggestion with Org-lint, or even writing a function that would
convert from the old to the new syntax, makes a shorter period
acceptable IMO.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-06-16 12:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 8:39 Tangling takes long - profiling and calling R Rainer M Krug
2015-06-15 8:42 ` Rainer M Krug
2015-06-15 18:52 ` Charles C. Berry
2015-06-16 10:29 ` Rainer M Krug
2015-06-15 19:49 ` Nicolas Goaziou
2015-06-16 10:34 ` Rainer M Krug
2015-06-16 11:46 ` Nicolas Goaziou
2015-06-16 12:45 ` Sebastien Vauban [this message]
2015-06-16 13:04 ` Nicolas Goaziou
2015-06-16 14:47 ` Rainer M Krug
2015-07-01 14:03 ` Aaron Ecay
2015-07-02 11:51 ` Nicolas Goaziou
2015-07-02 12:52 ` Rainer M Krug
2015-07-02 16:35 ` Aaron Ecay
2015-07-02 18:21 ` Sebastien Vauban
2015-07-02 18:44 ` Rainer M Krug
2015-07-02 18:43 ` Rainer M Krug
2015-07-02 16:11 ` Aaron Ecay
2015-07-03 13:43 ` Nicolas Goaziou
2015-07-02 18:51 ` Rainer M Krug
2015-06-16 14:42 ` Rainer M Krug
2015-06-16 21:45 ` Nicolas Goaziou
2015-06-17 7:16 ` org version numbers in file - WAS: " Rainer M Krug
2015-06-18 8:13 ` Nicolas Goaziou
2015-06-18 13:25 ` Rainer M Krug
2015-06-18 13:50 ` Nicolas Goaziou
2015-06-23 9:04 ` Rainer M Krug
2015-06-18 14:23 ` Detlef Steuer
2015-06-23 8:45 ` Rainer M Krug
2015-06-23 9:32 ` Detlef Steuer
2015-06-23 10:57 ` Rainer M Krug
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vriu616nrfcz.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).