Christian Moe writes:
> Could you give a pointer to your code? I'd like to try it.
Here it is again:
--8<---cut here---start->8---
;;
;; Kill any old org remnants
;;
;; clean load-path
(setq load-path
(delq nil (mapcar
(function (lambda
Best way to explain is with an example:
1. emacs -Q
2. eval this
(add-to-list 'load-path "~/src/org-mode/lisp/")
(require 'org-loaddefs)
Ensure that there is org-loaddefs available from git path.
3. M-x load-library ox-odt.el
4. Ensure (featurep 'org-odt) reports nothing.
5. M-x c
Carsten Dominik writes:
> On 31.8.2013, at 09:26, Achim Gratz wrote:
>> There is nothing to do here.
The new variables can and must be put in to a new groups.
> Thank you very much Achim.
If you cannot kill someone just ostracize them. Segregation CAN and
MUST be done.
Jambunathan K.
On 31.8.2013, at 09:26, Achim Gratz wrote:
> Carsten Dominik writes:
>> can someone please summarize this discussion for me and tell me what action
>> is required?
>
> There is nothing to do here. The "legacy" defcustoms are built into
> Emacs and are not easy to remove as there is no officia
> There is nothing to do here. The "legacy" defcustoms are built into
> Emacs and are not easy to remove as there is no official interface to do
> this. I have code that tries to do clean things up, but it may have
> unwanted side-effects depending on how the startup files are organized.
Hi, A
Carsten Dominik writes:
> can someone please summarize this discussion for me and tell me what action
> is required?
There is nothing to do here. The "legacy" defcustoms are built into
Emacs and are not easy to remove as there is no official interface to do
this. I have code that tries to do cl
Skip Collins writes:
> After I do an ODT export, many ox-odt variables are duplicated with
> old variable names:
> | [-]-\ Group Org Export ODT
> | | |--- Option Org Odt Schema Dir
> | | |--- Option Org Odt Content Template File
Above ones come from NEW exporter, ox-odt.el
>
Skip Collins writes:
> I started digging into this when I noticed some odd behavior while
> using ODT export. I think I am stuck using the older, buggier ox-odt
> and my setup is mixing two versions of org.
Your settings seem OK to me.
> 1) an odt file is generated (good)
This is what matters
Hi,
can someone please summarize this discussion for me and tell me what action is
required?
Thank you!
- Carsten
On 29.8.2013, at 20:25, Skip Collins wrote:
> Jambunathan K wrote:
>>> After I do an ODT export, many ox-odt variables are duplicated with
>>> old variable names:
>>>| [-]-\
Jambunathan K wrote:
>> After I do an ODT export, many ox-odt variables are duplicated with
>> old variable names:
>> | [-]-\ Group Org Export ODT
>> | | |--- Option Org Odt Schema Dir
>> | | |--- Option Org Odt Content Template File
>
> Above ones come from NEW exporter, ox-odt.el
Thanks Christian. That this behavior shows up in homebrew leads me to
suspect it might be happening on all platforms with recent Emacs,
unless steps are taken to eradicate the bundled org-mode. Exactly what
those steps should be is not clear to me. I suppose I could just
delete files inside Emacs.a
Hi,
I confirm that I see the same behavior, i.e. after ODT export old
variable names show up in the customize group, similar to what you show
below.
This is on GNU Emacs 24.3.1 on a Mac, installed with homebrew, with
Org-mode 8.0.7 installed via `make update2'.
This probably accounts for my pr
I think this is a bug. Can someone confirm? After I do an ODT export,
many ox-odt variables are duplicated with old variable names:
| [-]-\ Group Org Export ODT
| | |--- Option Org Odt Prettify Xml
| | |--- Option Org Odt Schema Dir
| | |--- Option Org Odt Content Template Fil
The version of org that comes with my stock Emacs on OS X (from
emacsformacosx.org) seems to conflict with my git installation of org.
This is particularly evident when trying to use ODT export. Emacs.app
is located in the usual /Applications folder. The newer org, which I
intend to completely supp
14 matches
Mail list logo
