From mboxrd@z Thu Jan 1 00:00:00 1970 From: Torsten Wagner Subject: Re: [RFC] Standardized code block keywords Date: Mon, 24 Oct 2011 10:06:58 +0900 Message-ID: <4EA4BA32.6080809@gmail.com> References: <87pqhrih3s.fsf@gmail.com> <30891.1319141196@alphaville.dokosmarshall.org> <87fwinifqu.fsf@gmail.com> <32184.1319143892@alphaville.dokosmarshall.org> <808vofwf1w.fsf@somewhere.org> <87y5wfgwn7.fsf_-_@gmail.com> <87lise5muh.fsf@gmail.com> <8039emxmvt.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58555) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RI90K-0007zf-Ak for emacs-orgmode@gnu.org; Sun, 23 Oct 2011 21:07:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RI90J-0008BV-AR for emacs-orgmode@gnu.org; Sun, 23 Oct 2011 21:07:04 -0400 Received: from mail-pz0-f47.google.com ([209.85.210.47]:45718) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RI90J-0008BQ-45 for emacs-orgmode@gnu.org; Sun, 23 Oct 2011 21:07:03 -0400 Received: by pzd13 with SMTP id 13so16574864pzd.6 for ; Sun, 23 Oct 2011 18:07:01 -0700 (PDT) In-Reply-To: <8039emxmvt.fsf@somewhere.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: Sebastien Vauban Cc: emacs-orgmode@gnu.org Hi Eric, Hi Seb, > > Eric Schulte wrote: >>> We could open an older file and if it isn't working, we could try >>> >>> #+PROPERTY: babel-function-set obsolete >> >> I think that making use of such a feature is almost as onerous as >> changing to the new terms (which is a simple search replace, in fact >> once terms are selected I'll happily share a function on list which can >> be used to convert all old terms in existing Org-mode files). Ok, I agree with both of you. Keeping obsolete functions active might be more difficult then just asking people to change the tiny bits and pieces. I like the idea to having a function to convert old syntax to new syntax (semi)automatically. Python did the same with there 2to3 script and I was able to convert large parts of my scripts without problems. Only make sure that the BIG BANG is really loud reaching all babelers out there (including the ones not on this mailing list and not reading changelogs) Maybe an additional function could be called for a certain time whenever old syntax is found (just a list of keywords) generating a warning that this code is obsolete pointing to a special chapter in the manual to help with conversion. That would help people to understand what is going on rather then getting a standard error message for code which run perfectly fine a few months ago. Remember, people might upgrade to emacs24 and they might not be aware that this includes updates to org-mode and org-babel. Anyhow I would like to offer to help with the manual (my lisp is to poor to help with coding). There should be a new section which helps old-babeler to change there code to the newest syntax, explain shortly changes in the syntax, etc. A two column table is often used for this | old syntax | replaced now by | | #+BABEL: | #+ PROPERTIES | Followed by some more explanation or a link to the (rewritten) manual section. Totti