From mboxrd@z Thu Jan 1 00:00:00 1970 From: Suvayu Ali Subject: Re: New exporter and defgroup Date: Fri, 19 Apr 2013 19:43:41 +0200 Message-ID: <20130419174341.GC3154@kuru.dyndns-at-home.com> References: <87ppxqbs2p.fsf@sbs.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59452) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTFLf-0002hG-EX for emacs-orgmode@gnu.org; Fri, 19 Apr 2013 13:43:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UTFLe-0005VK-FP for emacs-orgmode@gnu.org; Fri, 19 Apr 2013 13:43:47 -0400 Received: from mail-ea0-x22b.google.com ([2a00:1450:4013:c01::22b]:39318) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UTFLe-0005V2-8M for emacs-orgmode@gnu.org; Fri, 19 Apr 2013 13:43:46 -0400 Received: by mail-ea0-f171.google.com with SMTP id b15so1849694eae.30 for ; Fri, 19 Apr 2013 10:43:45 -0700 (PDT) Content-Disposition: inline In-Reply-To: <87ppxqbs2p.fsf@sbs.ch> 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: emacs-orgmode@gnu.org Hi Christian, On Fri, Apr 19, 2013 at 02:52:46PM +0200, Christian Egli wrote: > Hi all > > The new exporter engine has changed the defcustom names but seems to > have kept the names of the defgroups (at least in the case of > taskjuggler). This is good as it allowed me to make some > backward-incompatible changes. On the other hand when I do a M-x > customize-group RET org-export-taskjuggler I get a list of both the old > defcustom vars and the new ones. This is very confusing to the user as > you appear to have the same cutomizable var twice in the group. > > Is this a problem with my setup or is this inherent in the new exporter. > If the latter how can we deal with this? I think I have seen this before. Those old variables come from the shadowed older version of Org bundled with Emacs. Not sure if this can be avoided. Can we have some sort of a check while loading Org that picks up these shadowed variables and "deletes" them? My lisp foo is too bad to know if this is even possible. Hope this helps, -- Suvayu Open source is the future. It sets us free.