emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: New exporter and defgroup
Date: Fri, 19 Apr 2013 19:43:41 +0200	[thread overview]
Message-ID: <20130419174341.GC3154@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <87ppxqbs2p.fsf@sbs.ch>

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,


Open source is the future. It sets us free.

  reply	other threads:[~2013-04-19 17:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 12:52 New exporter and defgroup Christian Egli
2013-04-19 17:43 ` Suvayu Ali [this message]
2013-04-20  7:26   ` Bastien
2013-04-20  7:54     ` Achim Gratz

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:

  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=20130419174341.GC3154@kuru.dyndns-at-home.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).